Method and apparatus for managing digital files

ABSTRACT

A computer-implemented method of associating digital tags with digital files comprises storing a plurality of digital files having embedded therein content data and metadata including tags; receiving, via a user interface device of a client device, a first tag label containing alphanumeric text created and inputted by a user of the client device; modifying, using a controller device, a selected first one of the tags of the metadata in a first of the digital files to include the first tag label; receiving, via the user interface device or another user interface device, an instruction to search for all of the digital files having at least the first tag label; responsive to receiving the instruction, automatically searching for all of the digital files having at least the first tag label; and displaying, on a video display device associated with the client device, a first indication of the first tag label.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of and claims priority topending U.S. patent application Ser. No. 13/157,214, filed Jun. 9, 2011,which is incorporated herein in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to the management of digitalfiles and, more particularly, to a computer-implemented system andmethod for managing and using digital files such as digital photographs.

BACKGROUND OF THE INVENTION

Prior to the invention of digital photography, people tended to sharephotos by displaying printed copies in frames and albums, or would storethem in a container in hope of preserving these assets for future use orfuture generations. Important photos would often be inscribed on theback with significant details (people, location, event, etc.) topreserve the memory of that particular occasion. Many people would sharetheir memories by assembling an album that could be viewed with others.Occasionally, extra copies of special photos were printed for friends,relatives, etc. At one time, film slide shows were also a popular mediumfor sharing photo memories.

With the evolution of digital files, there has been explosive growth inthe number of individuals taking digital photos, converting old photosto digital copies, making movies and gathering digital documents and inthe sheer number of files people are capturing digitally. Today,virtually every personal computing device contains some kind of photo,movie or other type of digital file creator/player/viewer/storer/etc.

At the same time, there is little to no cost for people to store largeamounts of photos in various “containers” of the modern age. Facebook,Flickr, Shutterfly and countless other social media and specialtydigital files sites allow users to post and share images to a communitywith a frequency and ease that continues to feed the fire of the digitalrevolution. However, they don't allow much organization of digital tags,dynamic viewing of digital files, and the ability to export the digitalfiles with new digital tags. Questionable and ever-changing privacyterms for user/account information, including digital files, have alsoleft the marketplace leery of posting their full digital archive andassociated context to these sites.

What is needed to complement the widespread availability of digitalfiles is a medium that allows people to organize, view, preserve andshare these files with all the memory details captured, connected andvivified via an interactive interface. Such a solution would allowdigital files, including documents, photos, videos and audio, to tell afull story now, and for generations to come.

SUMMARY

In accordance with one embodiment, a computer-implemented method ofassociating digital tags with digital files comprises (1) storing, onone or more non-transitory computer-readable storage media, a pluralityof digital files, each of the digital files having embedded thereincontent data and metadata including tags; (2) receiving, via a userinterface device of a client device, a first tag label containingalphanumeric text created and inputted by a user of the client device;(3) modifying, using a controller device, a selected first one of thetags of the metadata in a first of the digital files to include thefirst tag label; (4) receiving, via the user interface device or anotheruser interface device, an instruction to search for all of the digitalfiles having at least the first tag label; (5) responsive to receivingthe instruction, automatically searching for all of the digital fileshaving at least the first tag label; and (6) displaying, on a videodisplay device associated with the client device, a first indication ofthe first tag label.

In another embodiment a computer-implemented method of associatingdigital tags with digital files comprises storing, on one or morenon-transitory computer-readable storage media, a plurality of digitalfiles, each of the digital files having a content data portion and ametadata portion including tags; displaying, on a video display deviceassociated with a client device, a first graphical representation of afirst tag label of a first of the tags and associated with a first ofthe digital files; receiving, via a user interface device of the clientdevice, a selection by a user of the client device of the firstgraphical representation of the first tag label as a search filtercriterion or a search string entered via the user interface devicecorresponding to the first tag label; responsive to the receiving,automatically searching through the digital files, using at least thefirst tag label as a search filter, for the digital files satisfying atleast the search filter criterion; and displaying, on the video displaydevice, an indication of the first tag label and a representation of thenumber of the digital files satisfying at least the search filtercriterion.

In accordance with a further embodiment, a web-based digital filestorage system comprises a digital file repository for storing andretrieving digital files; a digital tagging system permitting the userto assign a plurality of digital tags to each of the digital files,wherein the digital tagging system comprises at least one type of dataselected from the group consisting of a person's name, a location, arecipe, a date, a family relationship, a person's profile, an eventname, a rating, and a document type; a search filter, wherein the searchfilter allows the digital files to be searched according to a pluralityof types of data; and a user interface that presents the digital fileson a user's screen based on the digital tags, wherein the user interfacefurther comprises a digital tag image, the digital tag image having atleast one type of data represented thereon with text.

As described in detail below, the various embodiments providemuch-needed platforms that save a user significant time, providesignificant information with minimal screen space, and provide anappealing and customizable interface that will enhance the userexperience.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by reference to the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a screenshot of an organizational functionality view of oneembodiment of the disclosed system.

FIG. 2 is a screenshot of a photo detail view of one embodiment of thedisclosed system.

FIG. 3 is a screenshot of a gallery view of an event or album of oneembodiment of the disclosed system.

FIG. 4 is screenshot of an individual event or album view of oneembodiment of the disclosed system.

FIG. 5 is a screenshot of a location view of one embodiment of thedisclosed system.

FIG. 6 is a screenshot of a people thumbnail view of one embodiment ofthe disclosed system.

FIG. 7 is a screenshot of a people profile view of one embodiment of thedisclosed system.

FIG. 8 is a screenshot of a family tree view of one embodiment of thedisclosed system.

FIG. 9 is a screenshot of a timeline view of one embodiment of thedisclosed system.

FIG. 10 is a screenshot of a recipe chart, according to one embodimentof the disclosed system.

FIG. 11 is a screenshot of an album chart view of one embodiment of thedisclosed system.

FIG. 12 is a screenshot of an event chart view of one embodiment of thedisclosed system.

FIG. 13 is a screenshot of a people chart view of one embodiment of thedisclosed system.

FIG. 14 is a screenshot of a family tree chart view of one embodiment ofthe disclosed system.

FIG. 15 is a screenshot of a location chart view of one embodiment ofthe disclosed system.

FIG. 16 is a screenshot of a recipe chart view of one embodiment of thedisclosed system.

FIG. 17 is a screenshot of a slideshow view of one embodiment of thedisclosed system.

FIG. 18 is a screenshot of an advanced search filter view of oneembodiment of the disclosed system.

FIG. 19 is a screenshot of a homepage view of one embodiment of thedisclosed system.

FIG. 20 is a diagram of the Overall System Process Flow of MemoryWeb.

FIG. 21 is a diagram of the System for Reading Phase, SystemInterpreting, and Adding Digital File and Corresponding Data toRelationship Table Phase.

FIG. 22 is a table of the EXIF and MemoryWeb Tag Data Blocks

FIG. 23 is a table of the Microsoft Windows and MemoryWeb Tag DataBlocks.

FIG. 24 is a table of the MemoryWeb Person Tag Data Blocks.

FIG. 25 is a diagram of the Third Party Facial Recognition System.

FIG. 26 is a diagram of the Third Party Media System (Data Exchange).

FIG. 27 is a table of the User Settings Table.

FIG. 28 is a diagram of the Application Digital Tag Organizer System.

FIG. 29 is an illustration of the Application Dot-Tag Shape and Content.

FIG. 30 is a diagram of the Continuous Link of Application Dot-TagSystem.

FIG. 31 is an illustration of the Slideshow View of Digital File andApplication Dot-Tags.

FIG. 32 is a screenshot of People Application Views.

FIG. 33 is a screenshot of Collection Application Views.

FIG. 34 is a screenshot of Location Application Views.

FIG. 35 is screenshot of Uploads Application View.

FIG. 36 is a screenshot of Recipe Application View.

FIG. 37 is a diagram of the Advanced Filters System.

FIG. 38 is a screenshot of Adding the First Application Dot-Tag usingAdvanced Filter.

FIG. 39 is a screenshot of Single Application Dot-Tag Filter for EachApplication View.

FIG. 40 is a screenshot of Single Application Dot-Tag Filter for Date inUploads Application View.

FIG. 41 is a screenshot of the Single Application Dot-Tag Filter inLocation Application View.

FIG. 42 is a screenshot of Adding Another Application Dot-Tag Filter.

FIG. 43 is a screenshot of the Multi-Dot-Tag Filter in LocationApplication View.

FIG. 44 is a diagram of the Keyword Fast Search System.

FIG. 45 is a screenshot illustration of Using Keyword Fast Search.

FIG. 46 is a diagram of the Share to Third Party Social Network ProviderSystem.

FIG. 47 is a diagram of the Third Party Location Mapping System.

FIG. 48 is a diagram of the Share to Individual System.

FIG. 49 is a diagram of the Application Export System.

FIG. 50 is a table illustrating the Digital File Image File DirectoryData Blocks of JPG Photo within Microsoft Before and After MemoryWeb.

DETAILED DESCRIPTION OF ILLUSTRATED EMBODIMENTS

Although the invention will be described in connection with certainpreferred embodiments, it will be understood that the invention is notlimited to those particular embodiments. On the contrary, the inventionis intended to cover all alternatives, modifications, and equivalentarrangements as may be included within the spirit and scope of theinvention as defined by the appended claims.

The present disclosure relates to one or more of the following features,elements or combinations thereof. A web-based digital file storagesystem is disclosed. The storage system may include a digital filerepository for storing and retrieving digital files, such as photos, adigital tagging system configured to assign digital tags to the digitalfiles, a sorting system, and a user interface.

The digital tagging system may include various types of data, such as aperson's name, a location, a recipe, a date, a family relationship tothe user, an event name, a rating, sharing rights, file type and adocument name. The sorting system can allow the digital files to besearched and sorted according to a plurality of types of data and can beused for creating and organizing special views. The user interface maybe user-configurable, and can present the digital files on a user'sscreen based on these user inputs.

The digital file repository may be accessible over the Internet. Thesorting system may provide a user with the ability to search based on aplurality of digital tags. The disclosed system may also provide a wayto track relationships between users, so that a family tree can bedisplayed.

Recipes may also be linked to a person's name, with, for example, avideo and digital copy of original hand-written recipe to create arecipe view.

Moreover, the digital files and data can be exported as a single filewith the digital tagging embedded within the exported file.

In another embodiment, a method of storing digital photographs isdisclosed. The method may include the steps of storing a digitalphotograph in a file repository, associating a plurality of digital tagshaving different tag types with the digital photograph, providing asearch function that permits searching by a plurality of digital tagtypes and provides a search result, and providing a user-configurableoutput to display the search result. The digital tag types may include,for example, a person's name, a location, a recipe, a date, arelationship, an event name, a rating, file type and a document type.The method may include a further step of providing access to the filerepository via the Internet. The method may also allow for trackingrelationships between users so that a family tree can be displayed.

Additional features of the disclosure will become apparent to thoseskilled in the art upon consideration of the following detaileddescription of preferred embodiments exemplifying the best mode ofcarrying out the invention as presently perceived.

The presently disclosed method and application (herein alternativelyreferred to as a “system”) provides users with an Internet-basedinteractive platform to gather, organize, view, share and archivedigital files using a proprietary organization system and export taggingprocess. As used herein, the word “tag” refers to any type of digitaldata that can be assigned to a file to describe some aspect of that filethrough a tagging process. For images, the tagging is preferably in EXIFformat. For videos, documents and other file formats, any appropriateformat may be used. The disclosed system allows users to create, viewand share digital files, which could represent, for example, thememories a user has collected from the past and present, and couldincorporate additional memories for generations to come. As outlinedherein, various embodiments are disclosed that can accomplish these andother goals.

One disclosed embodiment includes an import feature. Users can importmedia files from users' favorite sources (e.g., computers, mobilephones, social networks, etc.). If any meta-tag information is embeddedwithin the media (e.g., date taken and GPS coordinates), the systemcould automatically read and utilize it for the user. Digital files,media, meta-tags, and other data discussed herein may be saved to one ormore file repositories (also referred to as a database herein).

In another aspect of the disclosed system, organizational functionalityis provided. Similar to the concept of writing certain information “onthe back of a photo,” the system's digital tagging system and organizingfeature allows a user to arrange large amounts of digital files withtags that can characterize and document the digital file(s). Digitalfiles can be individually or group organized at the same time for manytags including, but not limited to, a person's name, familyrelationships of the subjects to the user and between each other (e.g.,mother/father), location, date, event, album, comments, document type(e.g., birth certificate, poetry), recipe, ranking or rating, andsharing rights. Tags can be assigned to a single file at a time, or to aplurality of files at once. For example, if a user wishes to assign thetag “grandma” to 100 photos at once, the system provides a way for auser to select all 100 photos and enter the tag only once. An example ofthe manner in which digital photos can be organized is presented is seenin FIG. 1 .

Yet another feature is the multiple views from which a user can displayhis or her digital media files and their tagged attributes. Using a userinterface (e.g. a keyboard, mouse, or touch screen), users can selectindividual files, groups of files meeting specific criteria, or allfiles in their account from which to create views. These views mayalternately take the form of a chart. These views will be auto-populatedbased upon either tag information already associated with the digitalfile upon import or the tags assigned to the digital files by the userwithin the aforementioned organization functionality. Each digital filecan be enlarged, from any view or chart, by clicking an information(“i”) button to show an enlarged version of the digital media file withall the tags that are assigned to that digital file, as illustrated inFIG. 2 . In another embodiment, the user interface may beuser-configurable, as discussed further herein.

The following views are shown with particularity. In FIG. 1 , thegallery view allows the user to see all the digital media that areassociated within a group such as an event or custom album. The galleryview for either events or albums is illustrated in FIG. 3 .

As shown in FIG. 2 , an individual album or event view allows one to seethe files associated with a specific group. For example, one can viewthe digital files that relate to a group of files called “Trip to Italy2011.” The individual album or event view is illustrated in FIG. 4 .

A location view, as shown in FIG. 5 , identifies within an interactivemap (Google map shown as an example), where digital files were taken ororiginated. The location view can also provide additional outputs suchas a journey route that identifies the specific locations for an eventor trip that can be customized by users.

A people view, as shown in FIG. 6 , shows thumbnail photos of all thepeople in the system that can be clicked in for a people profile view. Apeople profile view, as shown in FIG. 7 , shows a profile picture of anindividual, their birth/death information, family relationships,overview (comments) on the person, as well as links to other views thatcontain that individual in the system.

A family tree view, as shown in FIG. 8 , can illustrate interactivefamily trees where one can see the family tree of an individual orfamily. If a user clicks on an individual within the family tree, itwill take him or her to the people profile view of that person.

The timeline view, as shown in FIG. 9 , will be an interactive timelinethat allows you to set ranges of digital files by year, month and day.The digital files shown in the timeline will also be interactive and ifthe user clicks on a digital file or group of digital files (e.g., eventor album), the user will then view the information related to thedigital file(s).

A recipe view, as shown in FIG. 10 , will show a recipe along with anydigital files that are associated with it. For example, a cherishedfamily recipe may show a digital copy of the original handwrittenrecipe, a photo of the family member who was the chef and a video of thefamily member making the recipe.

Each of the aforementioned views may also be seen in a chart format viewthat is interactive when any item on the chart is clicked, the user willthem be taken to a new screen that details all relevant digital files(and file types) for the clicked item.

For album or event chart views, as shown in FIGS. 11 and 12 , theelements listed in those charts will include individuals who are part ofeach album/event, number of digital files, date and other pertinentinformation.

A people view, shown in FIG. 13 , may demonstrate all the names ofindividuals that are in the system in an alphabetical listing. Such apeople view can also contain details on each person such as the numberof photos and videos that are associated with that person. The user canclick on that person to pull up the profile view of the individual orclick on the number of photos to see all the photos associated with thatperson.

In the family tree chart view, shown in FIG. 14 , family lineage can beviewed in multiple ways. For example, a user can set himself as the treeanchor and then see a tree of all people entered into the databaserelated to the user. The user could also set a contact as the treeanchor and then just view the descendants of that individual.

For a location chart view, as show in FIG. 15 , listings of all thelocations that are in the system are displayed along with the number ofdigital files, as well as names of persons associated with each. A usercan click on the location to see all the digital media files that areassociated with a specific location.

A recipe chart, as shown in FIG. 16 , can show recipes that uploaded tothe system. Along with the ingredients and steps of each recipe, thisview can identify the chef(s) name, number of photos and videosassociated with each.

For any of the views, the user can click on the digital file to start aslideshow feature that will allow them to scroll through an enlargedview of the digital file as illustrated in FIG. 17 .

Another aspect of the disclosure is the search filter. This filterallows users to select one or more criteria that will narrow down theirresults to just those digital files matching input criteria. The entiresystem can be filtered by, for example, key words (or plurality of keywords), event names, location, people, albums, star rating, file type,document type, and dates. A user may filter based on more than onecriterion at a time. To help users quickly identify digital files thatmay still need to be organized, the advanced search filter also allowsusers to isolate files that have no date, no location, no people, nospecific date/range, no upload date information or are lacking any othertag.

It should be noted that in one embodiment, searching via key word willsearch through all tagged information (user populated or auto-generatedupon import). For example, if a user searched for the term “Ohio,” thesystem would search for that term associated with any file in any way.If the user had files with Ohio as a state, file name, street name,person's name, file comment, etc., all would be retrieved.

Settings applied in the advanced search filter can cumulatively carryover to any subsequent pages until new criteria are selected. Forexample, a user can apply a filter to retrieve files associated with aparticular person. Then the user can set a date range to further narrowresults to show only those files for that selected person within thedate range. Any pages viewed from that point forward throughout theentire site would only contain files associated with person and the daterange specified. The advanced search filter is illustrated in FIG. 18 .

Yet another feature can be a user's homepage, as illustrated in FIG. 19, that can summarize the user's content within the system includingrelevant information in the system. It is contemplated that a user'shomepage may show a summary of the total number of photos, videos,documents and audio files that the user has uploaded. In thisembodiment, for each group of digital files (e.g., photos), the percentof files that has been organized with pertinent data such as date,name(s) and location can be noted. In addition, the homepage can show alist of people that are in the system and the respective count forphotos, videos, documents and audio files associated with each person.Also contemplated is a summary of the events, albums and locations thathave been entered into the system. The user homepage may serve as anexecutive summary dashboard of one's entire system and can be modifiedto provide data in an executive summary format for a user.

Another feature is that the entire system including the dynamic viewscan be presented in a wide range of user outputs—e.g. on the user'scomputer, smartphone or tablet display. The user may choose to presentthe digital files in any of the various types of ways disclosed herein.Other ways of outputting the files are also possible. The user cancreate and modify various sharing rights so that third parties may viewthe files and if desired, provide comments, apply tags or evendownload/copy the files for their own use.

Still another embodiment can provide export functionality. Once a userhas used the organization functionality to assign information to datafile(s), a user may want to export the data file in its original form(e.g., .jpg, .mp4, etc.) with the tags embedded within the digital filein the form of EXIF tags. In other words, a user can export his or herentire set of digital files, or may choose a subset based on keywordsand tags. The exported digital files can include key tags and attributesusers have assigned, and in one embodiment, such tags and attributes canbe embedded within the digital files. For example, each exported digitalfile may be imbedded with user-entered data such as the people,location, and event name. This feature will allow the users to back uptheir files to another source (e.g., external computer hard drive) or totransport it to another venue (e.g., another website that is used forviewing and/or sharing digital files such as a social media website)where it can be viewed with these attributes. This export feature canprovide users with the advantage of never losing key data that wasstored simply because the user chooses to move its digital files to anew digital archiving system.

A method is also disclosed. The method may include the steps of storinga digital file in a file repository, associating a plurality of digitaltags having different tag types with the digital file, providing asearch function that permits simultaneously searching by a plurality ofdigital tag types and provides a search result, and providing auser-configurable output to display the search result. The digital tagtypes may include, for example, a person's name, a location, a recipe, adate, a relationship between individuals, an event name, a rating, and adocument type.

Under the disclosed method, access may be provided to the repository viathe Internet. Relationships between users may also be tracked such thata family tree can be displayed. A recipe may also be linked to a user orperson. Finally, the method may include the step of outputting a digitalfile and its associated digital tags into a single file.

While the disclosure is susceptible to various modifications andalternative forms, specific exemplary embodiments thereof have beenshown by way of example in the drawings and have herein been describedin detail. It should be understood, however, that there is no intent tolimit the disclosure to the particular forms disclosed, but on thecontrary, the intention is to cover all modifications, equivalents, andalternatives falling within the spirit and scope of the disclosure asdefined by the appended claims.

A plurality of advantages arise from the various features of the presentdisclosure. It will be noted that alternative embodiments of variouscomponents of the disclosure may not include all of the featuresdescribed yet still benefit from at least some of the advantages of suchfeatures. Those of ordinary skill in the art may readily devise theirown implementations of a digital file organization system thatincorporate one or more of the features of the present disclosure andfall within the spirit and scope of the disclosure.

Application (also called “MemoryWeb Application” or “System”)—TheApplication is an online program constructed using a mix of freewarecode as well as custom-built proprietary coding with an interface thathas many functions including: 1) the ability to import, associate andembed Digital Tags to Digital Files by using existing Tags of a DigitalFile as well as the Application's custom Digital Tag options (alsocalled the Application Digital Tag Organizer) for use in theApplication; 2) view, sort, annotate, and share Digital Files from thevarious Application Views; 3) navigate using the proprietary ApplicationDot-Tag System; 4) filter Digital Files using the Application AdvancedFilter System or Fast Search System; 5) store the Digital Files throughan interactive Storage System through a User Relationship Table; and 6)export the Digital Files with the Digital Tags embedded within theDigital Files. This application has already been disclosed in U.S.patent application Ser. No. 13/157,214 and incorporated herein byreference. This application is also being trademarked as “MemoryWeb”with the US Commissioner for Trademarks on Dec. 26, 2013 underapplication No.: 86/152,930. The application may be accessible overvarious user interfaces that may use the Internet and via applicationsthat would be used on mobile communication devices such as smart phones(e.g., iPhones), Personal Digital Assistants (PDAs) and Tablets (e.g.,iPads).

Application Views—The Application Views utilizes the Application'sability to associate Digital Tags to Digital Files and display them incustomized views such as Uploads, Collections, Slideshow, Location,Timeline, Family Tree, People Profile, and Recipes.

Application Advanced Filter System—A function that provides searchcapabilities using one or more Digital Tags within the Application,resulting in a narrowed output display of the applied filters to displayone or more Digital Files and viewed in one or more Application Views.The Application Advanced Filter System can allow Digital Files to besearched and sorted according to a plurality of types of data and can beused for creating and organizing special views. The user interface maybe user-configurable, and can present the Digital Files on a user'sscreen based on these user inputs.

Application Dot-Tag—The manner in which a Digital Tag is displayedwithin the Application using pill-shaped indicators that can reside neara file's image or overlaid on the file's image. MemoryWeb Tags areillustrated as Application Dot-Tags within the Application to help theuser organize their Digital Files with key components of relatedinformation such as people, date of file, location, collection, starranking, and recipe. The MemoryWeb Application Dot-Tag is more than justtext (as traditional tagging systems) because Memory-Web ApplicationDot-Tags act as mini search engines that allow the user to see how manymatching files there are to that MemoryWeb Tag and if selected will takethe user to the corresponding Application View to illustrate the linkedsearch results of that Application Dot-Tag. However, it should beunderstood that other shapes and indicators are contemplated by thepresent invention, and may even be user-configurable. For example, theindicator may take the form of a sticky note, a different shape, a dotedshape, or any number of variations of indicators that may be functionalin displaying one or more words. Colors may also be used to indicatediffering categories of indicators, or differingassociations/intersection of the indicators. Within the pill-shapedindicator, the specific Digital Tag information is used to displayinformation about a Digital File. Throughout this document, theApplication Dot-Tag is shown as illustrated in FIG. 29 (indicators 0650,0654, 0655 and 0656).

Application Digital Tag Organizer System—Within the Application, afunction for assigning one or more Digital Tags to one or more DigitalFiles at the same time through the Application Dot-Tag Organizer System.This feature allows Digital Tags to be assigned to items such as photos,videos, audio files, and documents. The information created from thisfunctionality drives the outputs for the Application Views. TheApplication Digital Tag Organizer System will allow the tagging of keyitems as date, GPS location, star ranking, people (both name and facialrecognition), album(s), family relationships, a date, event name,sharing rights, file type, document name, and recipes. Each of theDigital Tags is user-configurable.

Application Export System—Ability to export Digital File(s) from theApplication, with the Digital Tags that were created within orimported/uploaded into the Application, embedded inside the DigitalFile. The Digital Tags within the exported Digital File can then beviewed and used by any other applications that can read EXIF tags.

Application Programming Interface (“API”)—The Application ProgrammingInterface (API) is the system that interacts with other communicationpoints or services over HTTP via a POST, GET, PUT, DELETE methods. TheAPI provides a way for users to access their MemoryWeb data outside ofthe web browser on mobile devices or other web connected devices. Theactions within the API deliver MemoryWeb Digital Files and Digital Tagsalong with all meta data associated with such files and tags.

MW Automatic Uploader/Downloader Application—Separate from the mainMemoryWeb Application, there are additional proprietary applicationscreated by MemoryWeb for user to upload and download (export) Digitalfiles to and from the main MemoryWeb Application. The first is the MWAutomatic Uploader/Downloader built for Window's compatible computers.The second is the MW Automatic Uploader/Downloader build for MACcomputer. Both of the MW Automatic Uploader/Downloader applications canbe installed on the user's computer to automatically upload the desiredDigital Files from their computer to the main MemoryWeb Application. Inaddition, the MW Automatic Uploader/Downloader applications allow forDigital Files to be exported from the main MemoryWeb Application to adesired folder on the user's computer with the updated tags embeddedwithin the Digital File.

Storage System—A storage system can be a cloud-based Storage System(e.g., Amazon's AWS, Dropbox, Box.net, Deutsche Telecom's Cloud, etc.),hard-drive, server, or any venue that allows one's information to bestored. The storage system would act as a database and file repositoryfor storage and retrieval of Digital Files to and from the Application.

Digital Files—An electronic file that can be in various file formats(e.g., PNG, JPEG, PDF, TIFF, MP3, MP4, WAV, and GIF) that are of itemssuch as photos, videos, audio files, and documents.

Digital Tags—The word “Digital Tag” refers to any type of digital datathat can be assigned to a file to distinguish and describe some aspectof that file through a tagging process. Digital Tags will be comprisedof various groups of digital data including:

-   -   a) EXIF Tags—EXIF stands for “Exchangeable Image File Format”        and is a standard that specifies the formats for images, sound,        video, and ancillary tags. The EXIF standard is an Open Standard        produced by the Standardization Committee and is detailed within        their document called Standard of the Camera & Imaging Products        Association. Standard of the Camera & Imaging Products        Association, CIPA DC-008 Translation-2012. Exchangeable image        file format for digital still cameras: EXIF Version 2. 3.        Established on April, 2010 and Revised on December, 2012.        Prepared by: Standardization Committee. EXIF tags are also        called “meta tags” or “metadata.” The EXIF information is        formatted according to the TIFF specification, and may be found        in JPG, TIFF, PNG, JP2, PGF, MIFF, HDP, PSP and XCF images, as        well as many TIFF-based RAW images, and even some AVI and MOV        videos. The EXIF meta information is organized into different        Image File Directories (IFD's) within an image. The names of        these IFD's correspond to the ExifTool family 1 group names.

When Digital Files are captured with digital cameras (includingsmartphones), scanners and other systems handling image, video and soundfiles, certain EXIF tags are automatically populated within the DigitalFile and can cover a broad spectrum of information such as:

-   -   Descriptions (e.g., Title, Subject, Star Ratings, Tags, People,        Comments)    -   Origin (e.g., Authors, Date taken, Copyright)    -   Image information (e.g., dimensions, color representation and        size)    -   Camera Setting Information (e.g., camera maker, camera model),        including static information such as the camera model and make,        and information that varies with each image such as orientation        (rotation), aperture, shutter speed, focal length, metering        mode, and ISO speed information.    -   Advanced Photo Information (e.g., lens maker, lens model,        contrast, brightness, EXIF version, etc.)    -   File Information (e.g., file name, item type (e.g., JPG file),        date created, date modified, size, etc.)    -   A thumbnail for previewing the picture on the camera's LCD        screen, in file managers, or in photo manipulation software.    -   Global Positioning System (GPS) information that is also known        as geocoding.    -   The Application will auto-populate any existing EXIF Tags from        the original Digital File upon upload into the Applications (as        illustrated in FIG. 21 ) and put this information into the Users        Relationship Table on the Storage System.    -   b) Extensible Metadata Platform (XMP)—This is Adobe's Extensible        Metadata Platform (XMP) format for labeling metadata within an        Adobe file.    -   c) Png Textual Data (tEXt)—This is Portable Network Graphics        (PNG) metadata format for labeling within a PNG file.    -   d) Microsoft Windows Tags—These are Microsoft Windows File        Attributes that are stored in Data Blocks from Microsoft's        system.    -   e) MemoryWeb Tags—These tags are typically developed within        MemoryWeb and can relate to People Names, Recipes, Collections,        Location Name, Family Relationships (also discussed in MemoryWeb        Person Tags), Social Network Data (e.g., ID, contact IDs, etc.),        File Folder Batch Name. This would be folder directory name that        includes the name of each folder that eventually leads to the        folder that the digital file was actually stored within the        User's PC. This is used to help the user organize data within        MemoryWeb based upon the users organization system used on their        PC. Facial Recognition Data, and other type of tags that are        user defined.    -   f) MemoryWeb Person Tags—These user defined tags within        MemoryWeb are specific to each person profile including such        areas as Nicknames, Birthdates, Date of Birth, Date of Death,        Biography, Family Relationships (e.g., Mother, Father, Brother,        Sister, Daughter, Son, Spouse, etc.), Pets, and Firsts (e.g.,        First Steps, First Words, First time riding a bike, etc.).

The combination of all the aforementioned tags is collectively referredto as “Digital Tags.” The list of groups and Digital Tag types will growas technology in this area improves over time. These Digital Tags arealso referred to as “File DNA” for MemoryWeb.

User Relationship Table—Within the Application, each User will store thedata related to Digital Files, Digital Tags, User Settings, and otherspecific information related to a User's repository of information iskept within the User Relationship Table.

Data Blocks—Within the User Relationship Table, there are Data Blocksthat will store information related to EXIF Tags, Microsoft WindowsTags, MemoryWeb Tags, and MemoryWeb Person Tags. These Data Blocks areused to generate the information that is displayed in such keycomponents such as the Application Views and Application Dot-Tags.Custom Code—Proprietary scripts and code developed by MemoryWeb toenable key functions such as Dot-Tag relationships and ability to embednew user-defined tags into a file and/or override existing EXIF tags andthe ability to navigate the application and it's functions viaconnections drawn from the associated tags

Open Source Libraries—Non-proprietary code taken from the free, opensource community integrated that is used by the Application.

User Interface—The Application may be accessible over various “UserInterfaces” including Personal Computers (e.g., Macs, Windows, etc.),Personal Digital Assistants (PDA) (e.g., iPhones) and Tablets (e.g.,iPad). The User Interfaces can be controlled through the Applicationusing various tools such as a keyboard, mouse, and touch screen.

The present invention relates to an Application that has many functionsincluding: 1) the ability to import, associate and embed Digital Tags toDigital Files by using existing Tags of a Digital File as well as theApplication's custom Digital Tag options (also called the ApplicationDigital Tag Organizer) for use in the Application; 2) view, sort,annotate, and share Digital Files from the various Application Views; 3)navigate using the proprietary Application Dot-Tag System; 4) filterDigital Files using the Application Advanced Filter System or FastSearch System; 5) store the Digital Files through an interactive StorageSystem through a User Relationship Table; and 6) export the DigitalFiles with the Digital Tags embedded within the Digital Files.

Prior to the invention of digital photography, people tended to sharephotos by displaying printed copies in frames and albums or would storethem in a container in hope of preserving these assets for future use orfuture generations. Important photos would often be inscribed on theback with significant details (people, location, and event) to preservethe memory of that particular occasion. Many people would share theirmemories by assembling an album that could be viewed with others.Occasionally, extra copies of special photos may have been printed forfriends, relatives, etc. At one time, film slide shows were also apopular medium for sharing photo memories.

With the evolution of Digital Files, there has been explosive growth inthe number of individuals taking digital photos, converting old photosto digital copies, making movies and gathering digital documents and inthe sheer number of files people are capturing digitally. Today,virtually every personal computing device contains some kind of photo,movie or other type of digital file creator/player/viewer/storer/etc.

At the same time, there is little to no cost for people to store largeamounts of photos in various “containers” of the modern age. Facebook,Flickr, Shutterfly and countless other social media and specialtyDigital Files sites allow users to post and share images to a communitywith a frequency and ease that continues to feed the fire of the digitalrevolution. However, they don't allow much organization of Digital Tags,dynamic viewing of Digital Files, and the ability to export the DigitalFiles with new Digital Tags. Questionable and ever-changing privacyterms for user/account information, including digital files, have alsoleft the marketplace leery of posting their full digital archive andassociated context to these sites.

What is needed to complement the widespread availability of DigitalFiles is a medium that allows people to organize, view, navigate,search, preserve and share these files with all the memory detailscaptured, connected and vivified via an interactive interface. Such asolution would allow Digital Files, including documents, photos, videosand audio, to tell a full story now, and for generations to come.

As disclosed in detail herein, the application provides the much neededplatform that saves a user significant time, provides significantinformation with minimal screen space, and provides an appealing andcustomizable interface that will enhance the user experience.

Anytime the MemoryWeb Application exchanges information with an externalStorage System or User Interface such as a phone, tablet, computer orother internet based user device, the interaction with the MemoryWebApplication involves Application Programming Interface (API). The API'sallow each system to call the specific Digital Files and Digital Tagsassociated with each request so they can be viewed.

Additional features of the disclosure will become apparent to thoseskilled in the art upon consideration of the following detaileddescription of preferred embodiments exemplifying the best mode ofcarrying out the invention as presently perceived.

The present disclosure relates to one or more of the following features,elements or combinations thereof. The Application allows the importationof Digital Files and then the association of Digital Tags to the DigitalFiles by using existing EXIF Tags of a Digital File as well as theApplication's custom organization of Digital Tags for use in theApplication. The Application then allows the Digital Files to be viewed,sorted, annotated, navigated, and shared using the various ApplicationViews. The Application can also filter Digital Files using theApplication Advanced Filter System functionality. The Digital Files canbe stored through a Storage System that interacts with the Application.In addition, the Application allows for Digital Files to be exportedwith the Application's Digital Tags embedded within the Digital Files.

The Application may be accessible over various user interfaces that mayuse the Internet and via applications that would be used on UserInterfaces such as Personal Digital Assistants (PDA) (e.g., iPhones) andTablets (e.g., iPad).

The presently disclosed Application provides users with an interactiveplatform to gather, organize, view, share and archive Digital Filesusing a proprietary organization system called the Application DigitalTag Organizer and export the modified Digital files with theApplication's Digital Tags embedded within the Digital Flies using theApplication Export feature.

The Application allows users to create, navigate, search, view and shareDigital Files, which could represent, for example, the memories a userhas collected from the past and present, and could incorporateadditional memories for generations to come. As outlined herein, variousembodiments are disclosed that can accomplish these and other goals.

Description of Embodiments

In FIG. 20 , the overall process flow of MemoryWeb is depicted. Each ofthe boxes depicted that are Inside the Memory-Web System (0050) aredetailed additional figures within this application. However, to helpillustrate the overall process flow, FIG. 20 was created. In FIG. 20 ,the process begins when original digital file(s) are uploaded toMemoryWeb (0101). This process can take place in a variety of waysincluding when a user manually selects uploads from the UploadsApplication View (see FIG. 35 indicator 1701), installs the a MWAutomatic Uploader/Downloader Application on their computer, or importsDigital Files from the users' other sources (e.g., mobile phones, socialnetworks, etc.).

Once a file is uploaded, the System Reading Phase (0100) begins.Information from the System Reading Phase is then sent to the SystemInterpreting and Adding Data to Relationship Table Phase (0200). Duringthis phase, information is passed back and forth to the Third PartyFacial Recognition System (0400) to the Third Party Facial RecognitionProvider (0401). The system will also coordinate between the Third PartySocial Media (Data Exchange) (0500) and then to various Third PartyMedia Providers (0501). Another key step from the System Interpretingand Adding Data to Relationship Table Phase is adding both the DigitalFiles and the corresponding tags to the User Relationship Table (0300).As illustrated in subsequent figures within the patent application, theUser Relationship Table serves as the key repository for all of theuser's data that generates virtually every display from the application.From the User Relationship Table, the user can use the ApplicationsDigital Tag Organizer System (0600), the Continuous Link of theApplication Dot-Tag System (0700), the Advanced Filters System (0800),or the Keyword Fast Search System (0900). The user can also shareDigital File(s) through the Share to Social Network Provider System(1000) to a Third Party Social Network Provider (0501) that is outsidethe MemoryWeb system or use the Share to Individual System (1200) to aPerson (1201) that is Outside the MemoryWeb system using the data fromthe User Relationship Table. To help generate some of the map views, thesystem will utilize a Third Party Geographical Mapping System (1100)that connects to a Third Party Geographical Mapping Provider (1101) thatis Outside the MemoryWeb system. The user can also export Digital Fileswith the Digital Tags embedded within the Digital File using theApplication Export System (1300) that will send a MemoryWeb ModifiedFile from MemoryWeb (1301) to a designated location by the User that isoutside the MemoryWeb system.

As illustrated in FIG. 21 , the System Reading Phase (0100) is describedin further detail. The System Reading Phase will first check if thedigital file is a duplicate file (0102) that is already in the User'scollection. If the file is a duplicate, it will not be uploaded (0104).However, if it is a new file for the user, the System Reading Phase willthen locate the EXIF Image File Directories in the digital file (0103)and then send that information to the System Interpreting and AddingData to Relationship Table Phase (0200).

As further illustrated in FIG. 21 , the System Interpreting and AddingData to Relationship Table Phase will take the EXIF Image FileDirectories sent from the System Reading Phase and read and iteratethrough each EXIF tag item (0201). At this time, the system willidentify faces from the digital file and then send this information tothe Third Party Facial Recognition System (0400) that will coordinatewith the Third Party Facial Recognition Provider (0401) that is outsidethe MemoryWeb. When the Third Party Facial Recognition System (0400)sends back data related to facial recognition of faces in the DigitalFile, it comes back then the system sends information related to peoplefacial recognition tags to the MemoryWeb Person Tag (Data Blocks) withinthe User Relationship Table (0300). The detailed process of the ThirdParty Facial Recognition System (0400) is further explained in FIG. 25 .

During the Read & Integrate Through Each EXIF Tag item (0201) theprocess will also upload a the original Digital File in MemoryWeb(0211), the process will also store a copy of the original file withinthe User Relationship Table (0300) and create five duplicate copies(0203) of different resolution sizes as follows: XL Duplicate File(0302, Large Duplicate File (0303), Medium Duplicate File (0304), SmallDuplicate File (0304), and a Thumbnail Duplicate File (0306). Eachduplicate file is used in different parts of the application dependingupon the photo size needed for such areas within the Application such asApplication Views, Application Dot-Tags, and Application Digital TagOrganizer System.

Another embodiment during the Read and iterate through each EXIF tagitem (0201) stage is determining if a MemoryWeb tag exists (0204). AMemoryWeb tag is a Digital Tag that is currently being used as anApplication Dot-Tag within the Application. If it is not a Digital Tagthat MemoryWeb is currently using, the application will Save EXIF datato the User Relationship Table for Digital File (0205) and send this tothe User Relationship table. This is done in case there are EXIF datathat are desired to be used in future releases of the Application. Forthe Digital Tags that are being used in the Application, the system willParse EXIF data into MemoryWeb Tags (0206), look up MW tag data (0207)and determine if a Digital Tag currently exists (0208). If a Digital Tagdoes not exist, the system will Create a new MW tag data ((0209) andsend this to the appropriate Data Blocks within the User RelationshipTable (0300). If Digital Tag data does exist, the system will Associateexisting tag data ((0210) to the appropriate Data Blocks within the UserRelationship Table (0300).

The third and final area within FIG. 21 is the System Indexing DigitalFiles and Tag Data Blocks for a Digital File within the UserRelationship table (0300). In the User Relationship Table, the user'sinformation system information stored such as User Settings (0390).Copies of the Original Digital File (0301), XL Duplicate File (0302,Large Duplicate File (0303), Medium Duplicate File (0304), SmallDuplicate File (0304), and Thumbnail Duplicate File (0306) are stored.The final area of the User Relationship Table relates to the data blocksincluding EXIF Tag (Data Blocks) (0320), Microsoft Windows Tag (DataBlocks) (0320), MemoryWeb Tag (Data Blocks) (0360), and MemoryWeb PersonTag (Data Blocks) (0380).

In FIG. 22 , there are two charts that illustrate EXIF and MemoryWeb TagData Blocks. The first chart illustrates the EXIF Tags Version 2.3 (DataBlocks) (0320). For the EXIF Tags Version 2.3 (Data Blocks) (0320), theinformation from this table is an expert from an Open Source Librarycode produced by the Standardization Committee that is detailed withintheir document called Standard of the Camera & Imaging ProductsAssociation. While all the EXIF tags that are contained within a DigitalFile are read (as previously illustrated in FIG. 21 within the SystemInterpreting and Adding Data to Relationship Table Phase (0200)) and arestored within the system's User Relationship Table (0300), a summary ofthe primary EXIF tags that are currently used within MemoryWeb areillustrated in the EXIF Tag Blocks (0320). The EXIF tag information isorganized into different Image File Directories (IFD's) or “Data Blocks”within an image and organized in the column heading of Tag Label (0321).The names of these IFD's correspond to an EXIF standard for Exiffoolfamily 1 group names that are depicted in the column heading of EXIFGroup (0322). The IFD's are stored within a specific data block locationwithin a Digital File and these locations have a standard name of thespecific location (0323) within the Digital File. The primary EXIF tagsthat are read and used by MemoryWeb to generate Application Dot-Tagsare: Description Title (0324), Description Rating (0325), Origin DateTaken (0326), Digital File Width (0327), Digital File Height (0328),User Comment (0329), GPS Latitude (0330), GPS Latitude Ref (0331), GPSLongitude (0332), and GPS Longitude Ref (0333).

In FIG. 22 , the second chart illustrates the MemoryWeb Tag (DataBlocks) (0360) that overlap with standard EXIF Tag blocks. As previouslyillustrated in FIG. 21 , the EXIF Tag Data blocks are read and broughtinto the User Relationship Table (0300). When the data is stored withinthe system's User Relationship Table, they are also stored with thecorresponding EXIF tag label as illustrated in the column calledMemoryWeb Tag (0361). For example, when a Digital File is brought intoMemoryWeb and the system reads the Origin Date Taken (0326) for the EXIFTag block, the system will denote this in the MemoryWeb table asMediaAsset.DateCreated (0364). This designation is very important as itallows MemoryWeb to re-inject any updated or new MemoryWeb Tag data intothe corresponding standard EXIF Tag blocks of a Digital File when it isexported from MemoryWeb (as previously illustrated in FIG. 20 with theApplication Export System (1300)). Continuing with this example, if theOrigin Date Taken is modified within the MemoryWeb system, when the fileis exported through the Application Export System (1300), the newupdated date from MemoryWeb (0364) will be mapped to the EXIF Tag Datablock with the Tag Label of Origin Date Taken (0326) with the EXIF Groupcalled ExifIFD (0334) and the Location called 0x9003 (0335).

In situations where there is no standard EXIF Tag data block for theMemoryWeb Tag for such items such as Collections, People Location Name,Recipe Name, etc. (0367), they are mapped to a general EXIF Tag datablock called User Comment (0329). As the standards for EXIF Tag datablocks change, the system can be mapped to any new specific EXIF Tagdata blocks. For example, if an EXIF Tag Data block is made for RecipeName, the MemoryWeb Tag related to Recipe Name will be mappedspecifically to that new EXIF Tag data block as opposed to User Comment.

In FIG. 23 , there are two charts that illustrate Microsoft Windows andMemoryWeb Tag Data Blocks. The first chart illustrates the standardWindows Imaging Component (WIC) Metadata (Data Blocks) (0340). MicrosoftWindows has their metadata tag blocks contained in areas called TagLabels (0341). The primary WIC Metadata data blocks that are read andused by MemoryWeb to generate Application Dot-Tags are: File Name (0342)and File Folder Path (0343). The corresponding MemoryWeb Tag data blocks(0360) for the WIC metadata tag blocks are called MediaAsset.Filename(0372) for the Microsoft file name and MediaAsset.UploadBatch.Batchname(0373) for the Microsoft File Folder Path. The ability for MemoryWeb toread the File Folder Path from Microsoft is a unique process used withinMemoryWeb to help the user organize their photos based upon theorganization methods they have already used within Microsoft. Forexample, if the user stored a group of photos on their Microsoftcomputer in the file directory C:/Photos/2013/First Day of School,MemoryWeb will automatically place the photos that were located withinthat Microsoft File Folder Path into a MemoryWeb Application Dot-Tagunder a collection called “First Day of School” based upon the lastfolder within the file folder path. An example of the ApplicationDot-Tag that would be generated from the File Folder Path is in FIG. 31with the label “First Day of School” (0770),In addition, MemoryWeb willallow the user to view the photos that are within a specific File FolderPath in the MemoryWeb Uploads Application View so that the user canorganize photos from the same File Folder Path. An example of how thiswill be illustrated within MemoryWeb's Uploads Application View is inFIG. 35 with the groping of photos with the File Path NameC:/Photos/2013/First Day of School (0709).

In FIG. 24 , the MemoryWeb Person Tag Data Blocks (0380) that arecontained with a User Relationship Table are illustrated. For any personthat is added within a user's account, various MemoryWeb Person Tag DataBlocks are stored including: Person Name (0395), Nickname (0381),Birthdate (0382), Date of Death (0383), Biography (0384), Mother (0385),Father (0386), Brother(s) (0387), Sister(s) (0388), Daughter(s) (0389),Son(s) (0390), Spouse(s) (0391), Facial Recognition (0392), FacebookID(0393), Pets (0394), and other data blocks that will be added in thefuture as the Application grows (0396). These data blocks are primarilyused in the People Profile Application View as illustrated in FIG. 32(indicator 1430). One embodiment within the MemoryWeb Person Tag DataBlock contains the FacebookID (0393). As illustrated in FIG. 26(indicator 0507), information from Third Party Media Providers will beexchanged within MemoryWeb and the user's FacebookID will be providedand stored within the MemoryWeb Person Tag Data Block. In addition, anyof the User's contacts from Facebook will also be downloaded into thecorresponding MemoryWeb Person Tag Data Blocks for any matching personswithin the User's MemoryWeb account. The information from the ThirdParty Media Providers that are stored within MemoryWeb will be used toprovide “push notifications” to the user for various items such as whenthe user or any one of its contacts posts a photo to that Social Mediavenue.

As illustrated in FIG. 25 , the Third Party Facial Recognition System(0400) is described in further detail. As photos are imported oruploaded into the Application, the systems will request thumbnailDigital Files (0404) from the User Relationship Table (0300). On aroutine basis (e.g., daily), the system will retrieve all the thumbnailsof Digital Files with unconfirmed faces (0403) and the send thoseDigital Files (0404) to the Third Party Recognition Provider (0401). TheThird Party Facial Recognition Provider (0401) uses their algorithms tofind location of eyes, nose, mouth and many other points for each facedetected in the photo. They will also determine gender, check if theperson is smiling, have eyes open, lips sealed or wearing glasses. TheThird Party Facial Recognition Provider will use their algorithms toassociate potential matches of faces for the user's collection ofphotos. For each face, the system will send back attributes includinggender (male, female), glasses (true, false), smiling (true, false),lips (sealed, parted), eyes, (open, closed), mood (happy, sad, angry,surprised, disgusted, scared, neutral), field in the response have twosubfields: value (string) and confidence (integer). For each attribute,the Third Party Facial Recognition Provider will assign percentages ofconfidence (0% to 100%) for each attribute that can be used by theMemoryWeb Application to utilize.

The Third Party Facial Recognition Provider will then send theinformation relating to a person back to MemoryWeb (0405). The MemoryWebApplication parse the identified faces and corresponding FacialRecognition data for each Digital File (0406). The system will interactwith the User Relationship Table and determine if the face is anexisting (i.e., “trained”) face in MemoryWeb where there is a Face ID inthe User Relationship Table (0407). If not, the system generates afacial recognition record for unknown person and then sends informationto MemoryWeb Person Tag (Data Blocks) in User Relationship Table (0410).If yes, the system will then determine if the face is above the system'sthresholds for confirming a face is a specific person in the user'sMemoryWeb system (0408). If no, system generates virtual unconfirmedfacial recognition record for person and then sends information toMemoryWeb Person Tag (Data Blocks) in User Relationship Table (0411). Ifyes, the system records and associates specific face for Digital Filewith a MemoryWeb Person ID and sends to MemoryWeb Person Tag (DataBlocks) in User Relationship Table (0409).

Typically, the ability to confirm and deny facial recognition matcheswill be within the People Profile Application View as illustrated inFIG. 32 within the facial recognitions area (indicator 1442). The systemwill also have other facial resonations area where the user can confirmor deny the suggested facial recognitions of a person for a DigitalFile. When the user denies the suggested facial recognition, the systemdis-associates potential person match Tag, search's the user'scollection for other potential matches, and then sends information toTag Data Block of Relationship Table for the Digital File. If the useraccepts the suggested facial recognition, the system sends this facialrecognition tag confirmation to the User Relationship Table for theDigital File. Once a confirmation is made, the newly associated DigitalFile will have that confirmed person Application Dot-Tag associated tothat Digital File for all Application Views. Each time an accepted ordenied facial recognition is made for a specific person, the specificdata points used for facial recognition is improved and sent to theThird Party Facial Recognition Provider for more accurate confirmationsof that person during the next run for that person.

As illustrated in FIG. 26 , the Third Party Media System (Data Exchange)(0500) is described in further detail. There are numerous types of thirdparty media systems that are contemplated for MemoryWeb including socialnetwork providers (e.g., Facebook, Twitter, and LinkedIn) and otherphoto sites (e.g., Flickr and Picasa). In addition, it is contemplatedfor the ability to print Digital Files from MemoryWeb using third partyprint providers such as Walgreens or Shutterfly. Further contemplatedsolutions might be from digital file warehouses such as Dropbox andbox.net. All of the Third Party Media Systems will interact withMemoryWeb using the same system that is described within FIG. 26 . TheThird Party Social Media System starts when the user initiates sharingof their information with Third Party Media Provider with MemoryWeb(0502). When this is initiated, the system will send registrationinformation (0503) to the Third Party Media Provider (0501). Oncereceived, the Third Party Media Provider will send back a confirmationwith the Third Party Social Media ID (0504) and then the system willsend the information (0505) to the User Settings Table (0390) within theUser Relationship Table (0300). The system will then send daily requestsfrom the User Relationship Table for contact names and IDs (0506) to theSocial Media Provider (0506). If there are new contact names that arenot part of the user's current people, the system will receive newcontact names and IDs from the Social Media Provider (0501). The userwill have the ability to confirm or deny matches (0508) with theircontacts within MemoryWeb. If there is a match, the system willassociate the existing person within MemoryWeb to the same ID of theperson within the Third Party Social Media platform (0509) and then sendthis to the User Relationship Table. If there is not a match, the systemwill add this additional contact as a new person and send (0510) this tothe User Relationship Table. If the user wants to share or print DigitalFiles from MemoryWeb, they can do this with the Share to Third PartyMedia Provider System (1000) that is further detailed within FIG. 46 .

In FIG. 27 , the MemoryWeb User Settings Table is illustrated. Asillustrated in the User Settings Table (1900), various data blocks ofinformation is stored including the User's Name (1901), Payment ID(1902) that is used with third party payment providers, Password (1903),Account Type (1904) (i.e., free or paid account), User's email (1905),Language preference (1906), Date format preference (1907), Emailnotification (1908) preferences, the ability to share Contacts (withthird Party Social Media) (1909), Facebook ID (1910), API Token (1911),Payment Date (1912) and other settings that will evolve as theApplication grows (1913).

In FIG. 28 , the Application Digital Tag Organizer System (0600) isillustrated. Within various Application Views the user can select, add,delete and edit MemoryWeb Tags for such areas as people, date, location,collections, star rankings, and recipes. An illustration of an UploadsApplication View where MemoryWeb Tags for a Digital File can beselected, added, deleted, or edited is illustrated in FIG. 35 . TheApplication Digital Tag Organizer System begins when the user selectsone or more Digital Files in MemoryWeb (0601). The system then sends arequest to the User Relationship Table for the specific Digital File(0602). The system then retrieves the Digital File and the Digital FileTag Data Blocks (0603) from the User Relationship Table (0300). Next,the system will display the Digital File and the corresponding DigitalFile Tag Data Blocks in the form of Application Dot-Tags (0604). Anexample of how the system can illustrate a Digital File with thecorresponding Application Dot-Tags is in FIG. 31 (indicators 0780, 0765,0766, 0768, 0770, and 0771).

If the user selects an Application Dot-Tag (0605), the system willutilize the Continuous Link of Application Dot-Tags System (0700) toproduce the results of that Application Dot-Tag within one of theApplication Views that is later illustrated in FIG. 30 .

If the user selects add for a MemoryWeb Tag (0606), the user can add anew MemoryWeb Tag. When the user begins to type in text to add a tag,the system will produce suggestions on matching MemoryWeb Tags or theoption to add a new tag (0607). If a matching tag is selected (0608),the system associates the new MemoryWeb tag to the Tag Block of theRelationship Table for the Digital File (0610). Alternatively, if thetag does not exist the user can create a new MemoryWeb Tag (0609) andthen the system associates the new MemoryWeb tag to the Tag Block of theRelationship Table for the Digital File (0611).

If the user selects edit for a MemoryWeb Application Dot-Tag (0612), theuser can add information text to edit the MemoryWeb Tag and the systemwill produce suggestions or matching MemoryWeb tags or the option to adda new tag (0613). If there is a match within the user's system, thematching MemoryWeb Tag will appear and the user can select the MemoryWebTag (0614). Once the matching tag is selected, the system associates thenew MemoryWeb tag to the Tag Block of the Relationship Table for theDigital File (0616). Alternatively, the user can create a new MemoryWebTag (0615) and then the system associates the new MemoryWeb tag to theTag Block of the Relationship Table for the Digital File (0617). If theuser selects delete for a MemoryWeb Application Dot-Tag (0618), thesystem deletes the association of MemoryWeb tag to Tag Data Block ofRelationship Table for Digital File (0619).

In FIG. 29 , the Application Dot-Tag Shape and Content is illustrated(0650). MemoryWeb Tags are illustrated as Application Dot-Tags withinthe Application to help the user organize their Digital Files with keycomponents of related information such as people, date of file,location, collection, star ranking, and recipe. The MemoryWebApplication Dot-Tag is more than just text (as traditional taggingsystems) because Memory-Web Application Dot-Tags act as mini searchengines that allow the user to see how many matching files there are tothat MemoryWeb Tag and if selected will take the user to thecorresponding Application View to illustrate the linked search resultsof that Application Dot-Tag (as illustrated in FIG. 30 ). In essence,the Application Dot-Tags operate as mini search engines for the user'sDigital Tags.

The structure of an Application Dot-Tag (0650) can take on an solid-lineenclosed shape of a pill, dot or similar depiction (0651) and within theshape the name of the MemoryWeb Tag is displayed (0653) along with thenumber of Digital Files (0652) that are also associated with that sameMemoryWeb Tag. FIG. 29 further illustrates more examples of theApplication Dot-Tags. If the number of Digital Files associated with aspecific MemoryWeb Tag is less than a certain number (e.g., 1000), theactual number of Digital Files associated with that MemoryWeb Tag isdisplayed. In FIG. 29 , this is illustrated with an Application Dot-Tagthat has 453 files that are associated with the location of Cologne,Germany (0654). However, if the number of Digital Files associated witha specific MemoryWeb tag are greater than the character length, agreater sign along with a number sequence that is less than the totalnumber of associated Digital Files will be displayed (0655). In FIG. 29, this is illustrated with an Application Dot-Tag that has “>999” (0657)as the number of Digital Files with the exact same MemoryWeb Tag and ifthe name of the MemoryWeb tag is longer than the text sequence, only aportion of the MemoryWeb tag will be displayed along with an ellipse asillustrated with “Holiday Photos from . . . ” (0658). Finally, theApplication Dot-Tag may be illustrated with a dotted or similardistinction (as opposed to a solid line) to help indicate a partialrelationship (0656). In the illustration in FIG. 29 , the dotted line isto indicate that only some of the selected Digital Files have theMemoryWeb Tag of Frank Smith.

In FIG. 30 , the Continuous Link of Dot Tag System is illustrated(0700). When a user selects an Application Dot-Tag, it will take them tothe corresponding Application View that relates to the type of MemoryWebTag. The Continuous Link of Application Dot-Tag System begins when auser selects an Application Dot-Tag (0701).

If the Application Dot-Tag is a Person (0702), the system will send arequest to display the requested information (0708) to the UserRelationship Table (0300). A sample illustration of how a user canselect a person Application Dot-Tag is in FIG. 31 (indicator 0764). Fora person tag, the system receives data for that person from the UserRelationship Table and displays the relationship data in a PeopleProfile View (0709). A sample illustration of a selected PersonApplication Dot-Tag is in FIG. 32 (indicator 1430).

If the Application Dot-Tag is a Collection (0703), the system will senda request to display the requested information (0708) to the UserRelationship Table (0300). A sample illustration of a collectionApplication Dot-Tag that can be selected is in FIG. 31 (indicator 0781).For a collection tag, the system receives data for that collection fromthe User Relationship Table and displays the relationship data in aCollection View (0710). A sample illustration of a selected CollectionApplication Dot-Tag within a Collection View is in FIG. 33 (indicator1530).

If the Application Dot-Tag is a Location (0704), the system will send arequest to display the requested information (0708) to the UserRelationship Table (0300). A sample illustration of a locationApplication Dot-Tag that can be selected is in FIG. 31 (indicator 0768).For a location tag, the system receives data for that location from theUser Relationship Table and displays the relationship data in a LocationView (0711). A sample illustration of a selected Location ApplicationDot-Tag within a Location View is in FIG. 34 (indicator 1630).

If the Application Dot-Tag is a Date (0705), the system will send arequest to display the requested information (0708) to the UserRelationship Table (0300). A sample illustration of a date ApplicationDot-Tag that can be selected is in FIG. 31 (indicator 0766). For a datetag, the system receives data for that date from the User RelationshipTable and displays the relationship data in Uploads View with that datefiltered (0712). A sample illustration of a selected Date ApplicationDot-Tag within Uploads View is in FIG. 40 (indicator 0861).

If the Application Dot-Tag is a Recipe (0706), the system will send arequest to display the requested information (0708) to the UserRelationship Table (0300). For a recipe tag, the system receives datafor that recipe from the User Relationship Table and displays therelationship data in a Recipe View with that date filtered (0713). Asample illustration of a selected Date Application Dot-Tag within RecipeView is in FIG. 36 (indicator 1800).

The Application is contemplated to have additional types of ApplicationDot-Tags (0707) in the future including Family Trees, Timespan, etc. andeach of these MemoryWeb Tags will go through the same continuous link ofApplication Dot-Tag process. For an additional type of ApplicationDot-Tag, the system will receive data from the User Relationship Tableand displays the relationship data in the corresponding view for thattype of Application Dot-Tag (0714).

If within any of the Application Views the user selects a Digital File(0715), the Digital File is then displayed in a Slideshow View (0716)where the user can again select an Application Dot-Tag (0701) and startthe continuous link of Application Dot-Tag functionality over again.Also within an Application View, if the user selects another ApplicationDot-Tag (0717), the entire continuous link of Application Dot-Tagfunctionality begins again and sends the request back to ask if thenewly selected Application Dot-Tag is a person (0702).

In FIG. 31 , the Slideshow view of a Digital File, Application Dot-Tags,and comments are illustrated (0750). When viewing a Digital File orgroup of Digital Files within the Slideshow Application View (0750), theselected Digital File is displayed in the center of the screen (0754).If the user wants to export this photo with all the associated MemoryWebTags, they can select export (0751) which will initiate the ApplicationExport System as illustrated in FIG. 49 . If the user wants to see theDigital File that is one file before the selected Digital File, theyselect the left arrow (0752) or they can select the right arrow (0753)to display the next photo in the sequence. Below the Digital File, thecomments (0755) that are specific to that Digital file are depicted. Ifthe user wants to edit the comments, they select edit (0756). If theuser would like to see a moving slideshow of all the photos that arepart of the group of Digital Files, they can select on the play sign(0757) or simply click the specific thumbnail of a Digital File (0758)to be displayed. The user can also have the slideshow in a full screenslideshow by selecting the full screen icon (0759). If the user wants toshare the individual Digital file via email, they can select the mailicon (0760) or share it through a third party median provider, in thiscase Facebook (0761). A more detailed description on how the sharefunctionality works is in FIG. 46 (indicator 1000).

In FIG. 31 , each Application Dot-Tag that is associated with a DigitalFile is illustrated to the right of the Digital File under each majorMemoryWeb Tag area. For this example, the People area (0763) hasApplication Dot-Tags of Jackson Smith (0780) and JC Smith (0764)associated with the selected Digital File. In the Dates area (0765), theApplication Dot-Tag of Aug. 28, 2013 (0766) is associated with theselected Digital File. In the Locations Area (0767), the ApplicationDot-Tag of Abe Lincoln Elementary School (0768) in the locationassociated with the selected Digital File. In the Collections Area(0769), the Application Dot-Tags of First Day of School (0770) andJackson and JC Photos 2013 (0771) are associated with the selectedDigital File. The Star Rankings Area (0782) shows that four out of fivestars (0773) was selected for this Digital File. If the Digital File isassociated with a Recipe (0774) the Application Dot-Tag would beillustrated in this area. The Media Type area indicates that this is aMemento (0776). If the user wants to delete this Digital File from theApplication, they can select the Delete Item function (0779). If theuser wants to edit the Application Dot-Tags, they can select the editicon (0762) and all the MemoryWeb Tag areas will be in edit mode aslater illustrated in FIG. 35 . Finally, any original Digital File detail(e.g., file name, camera specifications, etc.) is illustrated (0778).

In FIG. 32 , both of the People Application Views are illustrated. Thefirst People Application View (1400) is used to display all the peoplethat were created within the user's Application. This view can be seenby selecting “People” (1401) from any of the Application Views withinthe Application. The people can be listed in various sort orders thougha drop-down (1402) such as: Newest to Oldest (added), Oldest to Newest(added), Alphabetical (A-Z), Alphabetical (Z-A), etc. Additional sortsare contemplated such as age sort. For each person, a thumbnail of theirface along with their name is depicted. In this figure, Jon Smith (1403)and JC Jon Smith (1404) along with some other people are illustrated.Also, the user can determine if they want to have 20, 50 or 100 peopleshown at one time (1405) by selecting the corresponding number box. Atthe top of every Application View within the Application, the user canselect Fast Search (1450) that is further described in FIG. 44 . Also atthe top of every Application View within the Application, the user canselect Apply Filters (1451) that is further described in FIGS. 37-43 .

In the second People Application View within FIG. 32 , a single peopleprofile (1430) is illustrated. The individuals name is displayed at thetop of the page (1431) along with their Nicknames (1433), when they wereBorn (1434), who their parents are (1435), Siblings (1436), Children(1437), and the person's Biography (1438). The Person Profile Photo ofthat individual is illustrated (1439) and if the user wants to changethe profile photo, they can change by selecting change profile photo(1440). For each person, the system can allow the user to quickly seeall the tags that are associated to a person. In this example, thesystem illustrates that there are four photos (1452) associated withthat person and will also illustrate thumbnails of each of the fourphotos (1446). These thumbnails can be selected and then the user willbe taken to the slideshow view for that Digital File. If the userselects Collections (1441), all of the collections that the person hasbeen tagged within will be displayed. If the user selects FacialRecognitions (1442), all the faces that are confirmed or need to beconfirmed are displayed. This is the area where the user can select toconfirm or deny a suggested facial recognition through the Third PartyFacial Recognition System that is illustrated in FIG. 25 . If the userselects Locations (1443), all of the Locations that the specific personhas been tagged within will be displayed. If the user selects FamilyRelationships (1444), the seven people that the user is associated withwill be displayed in a family chart or tree. If the user selects Recipe(1445), all the recipe's that the user has been tagged within will bedisplayed. If the user wants to edit any details within the individualpeople profile, they can select edit (1447) and all the fields willallow the ability to edit the details. If the user selects any of theApplication Dot-Tags such as the individuals mother Jane Smith (Doe)(1449), the application will utilize the Continuous Link of ApplicationDot-Tag System (see FIG. 30 ) and take the user to an individual peopleprofile view of Jane Smith (Doe). If the user selects View all People(1432), the Application will go back to the multiple People View (1400).

In FIG. 33 , both of the Collection Application Views are illustrated.The first Collection Application View is used to display all thecollections that were created within the user's Application (1500). Thisview can be seen by selecting “Collections” (1501) from any of theApplication Views within the Application. The collections can be listedin various sort orders though a drop-down (1502) such as: Newest toOldest (added), Oldest to Newest (added), Alphabetical (A-Z),Alphabetical (Z-A), etc. For each collection, a thumbnail of a DigitalFile from that collection depicted. In this figure, Smith Family Photos(1503), Europe Trip (1504), First Day of School (1505), Jackson and JCPhotos 2013 (1506), and Baseball Games (1507) is illustrated. At the topof every Application View within the Application, the user can selectFast Search that is further described in FIG. 44 . Also at the top ofevery Application View within the Application, the user can select ApplyFilters that is further described in FIGS. 37-43 .

In the second Collections Application View within FIG. 33 , a singlecollection (1530) is illustrated. The individual collection name isdisplayed at the top of the page (1532). Thumbnails of each Digital Filewithin the specific collections are illustrated. In this example, thesystem shows photos (1533) associated with the Smith Family PhotosCollection. If the user wants to edit any Digital Files within thecollection, they can select edit (1535) and then the user can add ordelete any Digital Files as well as set the cover photo for acollection. If the user wants to share this collection (1534), they canselect a method to share and this will take the user through the Shareto Third Party Media Provider System illustrated later in FIG. 46 . Ifthe user selects View all Collections (1531), the Application will goback to the multiple Collection View (1500).

In FIG. 34 , both of the Location Application Views are illustrated. Thefirst Location Application View is used to display all the locationsthat were created within the user's Application (1600). This view can beseen by selecting “Locations” (1605) from any of the Application Viewswithin the Application. The locations can be listed in various sortorders though a drop-down (1606) such as: Newest to Oldest (added),Oldest to Newest (added), Alphabetical (A-Z), Alphabetical (Z-A), etc.For each location, a thumbnail of a Digital File from that locationdepicted. In this figure, Wrigley Field (1601), Abe Lincoln ElementarySchool (1602), Home Sweet Home (1603), and Stonehenge (1604) isillustrated. What is also contemplated instead of a Digital File fromthat location is that a zoomed in image of a map from the specificlocation using the Third Party Geographical Mapping System laterdepicted in FIG. 47 . At the top of every Application View within theApplication, the user can select Fast Search that is further describedin FIG. 44 . Also at the top of every Application View within theApplication, the user can select Apply Filters that is further describedin FIGS. 37-43 .

In the second Locations Application View within FIG. 34 , a singlelocation (1630) is illustrated. The individual location name isdisplayed at the top of the page (1632). Thumbnails of each Digital Filewithin the specific collections are illustrated. In this example, thesystem illustrates a one photo (1633) taken at Wrigley Field (1634) thatis associated with the location called Wrigley Field. If the user wantsto edit any Digital Files within the collection, they can select edit(1637) and then the user can add or delete any Digital Files. If theuser wants to share the Digital Files associated with this location(1636), they can select a method to share and this will take the userthrough the Share to Third Party Media Provider System illustrated laterin FIG. 46 . If the user selects View all Collections (1631), theApplication will go back to the multiple Collection View (1600). As partof the individual Location View, an interactive map displaying azoomed-in image of the specific location is displayed (1635).

In FIG. 35 , the Uploads Application View and how it uses theApplication Digital Tag Organizer System is illustrated (1700). Similarto the concept of writing certain information “on the back of a photo,”the system's digital tagging system (also called Application Digital TagOrganizer) allows a user to select large amounts of Digital Files andadd Digital Tags that can characterize and document the digital file(s).Digital Files can be individually or group organized at the same timefor many tags including, but not limited to, a person's name, familyrelationships of the subjects to the user and between each other (e.g.,mother/father), location, date, album, comments, document type (e.g.,birth certificate, poetry), recipe, ranking or rating, and sharingrights. One or more Digital Files can be selected at the same time anddisplayed with an overlaid check mark when activated (1705 and 1710) andthen Digital Tags can be assigned to a single file at a time or to aplurality of files at once. For example, if a user wishes to assign thetag “grandma” to 100 photos at once, the system provides a way for auser to select all 100 photos (1713) and enter the tag only once. Inaddition, the system does include an indicator that appears when a userhovers over the Digital File providing all the relevant Digital Tagsassociated with that specific Digital File (1737) and in this example itshows the caption of “Family Smith finally sees Stonehenge,” that fourPeople are tagged to this photo, one collection is tagged to this photo,there are zero people recognized through Facial Recognition, and thedate of this photo is from Dec. 21, 2013. If the user wants to delete asingle photo from uploads, they can click on the “x” (1735) that isdisplayed when the user hovers over the Digital File thumbnail. Whenthere are multiple Digital Files, the user can determine how many imagesare displayed at one time in the Items Per Page Buttons (1738) thatinclude such numbers at 20, 50 and 100 on the page at the same time.When there is are more Digital Files that items per page, they areautomatically grouped by pages and a Page Button (1739) can be selectedto see the next set of Digital Files.

In the Uploads Location View, Digital Files can be directly uploaded tothe Application by selecting Upload Files (1701) and the user will havethe option to select the specific Digital Files to be uploaded fromtheir Storage System. Users also have the option to install theMemoryWeb Download Application that can be installed on either aMicrosoft or MAC computer that will automatically upload and sync photosto and from the users Storage System to the MemoryWeb Application. Alsodisplayed is the amount of space being used by the user within theApplication (1702). Uploads of Digital Files can be listed in varioussort orders though a drop-down (1703) such as: Newest to Oldest (added),Oldest to Newest (added), Alphabetical (A-Z), Alphabetical (Z-A), etc.In addition, the Digital Files can be sorted by File Batch Name (A-Z) orFile Batch Name (Z-A). In FIG. 35 , the sort of File Batch Name (A-Z) isselected (1703) and this provides three groups of Digital Files with thenames File Folder C:/2013/Family Fun (1704), File Folder C:/2013/General(1706), and of File Folder C:/2013/First Day of School (1709). The FileBatch Name is created when Digital Files are uploaded to theApplication. The File Batch Name allows the user to see the filedirectory of how they had their Digital Files stored from anotherStorage System (e.g., on their computer hard drive) that allows foreasier organization within the MemoryWeb Application. For example, inthe sort of File Folder C:/2013/General (1706), two digital files (1707and 1708) are illustrated that came from the exact same file folder pathof the Users Storage system upon upload. At the top of every ApplicationView within the Application, the user can select Fast Search that isfurther described in FIG. 44 . Also at the top of every Application Viewwithin the Application, the user can select Apply Filters that isfurther described in FIGS. 37-43 .

On the right side of FIG. 35 , the associated Application Dot-Tags alongwith the ability to organize one or more Digital Files at the same timeis illustrated. At the top of the screen, it shows how two Digital Filesare selected (1712) that correspond to the selected (checked) DigitalFiles (1705 and 1710). Below this area illustrates all the ApplicationDot-Tags that are associated with the two selected Digital Files. Theuser has the option to select all (1713) the Digital Files being viewedin the Uploads View as well as selecting none (1714). By selecting all,the user can administer Application Dot-Tags to all the selected DigitalFiles at the same time. If the user wants to delete Digital Files, theycan select the Digital Files to be deleted and then select the DeleteSelection (1715) option.

In FIG. 35 , each Application Dot-Tag that is associated with theselected Digital File(s) is illustrated. For this example, the Peoplearea (1716) has Application Dot-Tags of Jackson Smith (1734), Jane Smith(1733), Jon Smith (1731, and JC Smith (1717) that are associated withthe two selected Digital Files (1710 and 1705). If the user wants to adda person to all the selected Digital Files, they can click on “+AddPeople” (1718) that will display a pop-up where the user can search foran existing person within the user's existing people within theApplication or add a new person to the user's group of people within theApplication. It is contemplated to have a Facial Recognition suggestionsappear in this area of the Application that will allow users to confirmor deny a recognized person to a specific Digital File. However, thecurrent version of the People area is useful for situations where a faceis not recognized, but the user desires to tag a person to a DigitalFile, they can manually assign a Person Application Dot-Tag to thatDigital File for an existing person (e.g., if the person's back isturned, it is a document that contains that person, a piece of artcreated by that person, etc.).

In the Dates area (1719), the organize functionality for assigning aDigital Tag of a date within the Digital File(s) is illustrated. Uponupload, the date when the Digital File was created is automatically readby the Application and illustrated as an Application Dot-Tag (1720 and1730). As illustrated in the Dates area, the Application Dot-Tags ofJul. 4, 2013 (1720) and Aug. 28, 2013 (1730) are illustrated as theycorrespond to the dates that are associated with each of the selectedDigital Files. If the user wants to change the date for all the selectedDigital Files, they can click on “+Add/Edit Date” (1721) that willdisplay a pop-up where the user can add a new date for the selecteddigital files within the Application. This is a very useful feature whenan incorrect date is assigned to a digital file (e.g., if a photo fromOct. 31, 1951 was digitized on Dec. 31, 2012, the digitized dates wouldshow as an Application Dot-Tag that the user can change in this sectionto the correct date of Oct. 31, 1951).

In the Locations area (1722), the organize functionality for assigningDigital Tags of locations within the Digital File(s) is illustrated.Upon upload, the GPS location of where the Digital File was created (ifapplicable) is automatically read by the Application and illustrated asan Application Dot-Tag for locations of the selected files. In thelocations area, the Application Dot-Tags of Abe Lincoln ElementarySchool (1723) and Wrigley Field (1735) are illustrated as theycorrespond to the locations that are associated with each of theselected Digital Files. If the user wants to change the location for allthe selected Digital Files, they can click on “+Add/Edit location”(1724) that will display a pop-up where the user can search for anexisting location within the user's existing locations within theApplication or add a new location to the user's group of locationswithin the Application. Another added function to assign a location tothe selected Digital Files is to use Search with Map (1732) thatutilizes the Application's Third Party Geographical Mapping System thatis further illustrated in FIG. 47 that allows the user to type in anyrelevant information (e.g., location name, address, state, etc.) andthen the Application will search and pinpoint that location on a map.

In the Collections Area (1725), the organize functionality for assigningDigital Tags of albums within the Digital File(s) is illustrated.Digital Files can be associated to multiple albums. As illustrated inthe Collections area, the Application Dot-Tags of First Day of School(1726), Jackson and JC Photos 2013 (1727), and Baseball Games (1728) areassociated with the Collections for the selected Digital Files. If theuser wants to add a Collection to all the selected Digital Files, theycan click on “+Add/Create Collection” (1729) that will display a pop-upwhere the user can search for an existing Collection within the user'sexisting Collections within the Application or add a new Collection tothe user's group of Collections within the Application.

Within the Uploads View, the ability to perform similar tagging of StarRankings, Recipes, Family Relationships, and Media Types/Document Typeare also contemplated as part of the Application Digital Tag OrganizerSystem. For Star Rankings, it is contemplated to assign MemoryWeb Tagsof star rankings within the Digital File(s). Upon upload, if the starranking is already contained within the Digital File, it isautomatically read by the Application and illustrated as an ApplicationDot-Tag. The user can select one or more Digital Files and then apply astar ranking between 1 and 5 in the Uploads Application View. ForRecipes, it is contemplated to assign MemoryWeb Tags of Recipes toDigital File(s). The user can select one or more Digital Files and thentype within the “Recipe” search bar to either add a new recipe orassociate the Digital File(s) to an existing recipe. Digital Files canbe associated to multiple recipes. For Media Type/Document Type, theuser can choose from a list of common document types (e.g., BirthCertificate, Death Certificate, Marriage Certificate, etc.) can beutilized for common document type associations. Once a document type isassigned to one or more Digital Files, the document type appears withinan Application Dot-Tag. Digital Files can be associated to multipledocument types.

In FIG. 36 , an individual recipe view (1800) allows one to see all theinformation that is associated with a specific recipe. The name of thespecific recipe is displayed at the top of the page (1801) and thePeople Profile picture of the “chef” associated with the recipe isillustrated (1804). If no chef is assigned, the user can select the“+add/edit chef” (1803) to either choose an existing person from theuser's People in the Application or add a new person.

The view of various Digital Files within the recipe (1808) along withscrolling through the Digital Files using the arrow icons (1814 and1815), the ability to share this recipe with others by selecting thesharing icon (1812), As the Digital Files are selected on using the filmstrip on the bottom, a larger thumbnail illustrating the Digital File isshown (1807). The recipe view also allows you to choose a chef for therecipe from the people within the user's Application. When a chef isselected, the profile picture (1804) of the person along with their nameas an Application Dot-Tag (1816) is displayed. For each recipe, the usercan insert the ingredients (1809), directions (1810), and comments(1811). Each of these areas can be edited by selecting the edit button(1813). Another contemplated feature allows the user to apply starrankings for the recipe as well as categorize they type of recipe (e.g.,appetizer, entrée, etc.). It is further contemplated that the DigitalFiles within the individual recipe view may also include videos wherethey can be watched showing the chef making the recipe. It is alsocontemplated that the recipes will be interactive with external sources(e.g., the Food Network) so that recipes can be shared or imported withthe Application and that visitors to the account will be able topost/share comments about the recipe. It is further contemplated thatthe user can print the recipe using a print icon.

In FIG. 37 , the Advanced Filters System is illustrated (0800). Thisfeature allows the user to narrow the Digital Files being viewed withinthe Application Views by searching the user's entire collection ofMemoryWeb Tags within the Application and then displaying the filteredinformation in one of the Application Views. Advanced Filters System canbe filtered by such items as key words (or plurality of key words),event names, location, people, albums, star rating, file type, documenttype, and dates. A user may filter based on more than one criterion at atime. To help users quickly identify Digital Files that may still needto be organized, the advanced search filter also allows users to isolatefiles that have no date, no location, no people, no specific date/range,and no upload date information or are lacking any other tag. TheAdvanced Search Filter can be used within many of the views theApplication to narrow the set of Digital Files being viewed. Forexample, you can use the Advanced Filter Button to only show the mapview of locations a specific person has traveled in their lifetime.

When a user selects the “Advanced Filters” from almost any ApplicationView (0801) (the button can be seen in FIGS. 32, 33, 34, 35, and 36 ), apop-up will appear that allows the user to type in text into the textbox (0802). As the user is typing, the system sends a request (0803) tothe User Relationship Table (0300) to look up any possible MemoryWeb Tagmatches. The system will then produce the request (0804) and illustratethe potential matches of the filters to the user (0805). As the usertypes in another letter, the process of sending a request (0803) to theUser Relationship Table (0300), producing results (0804) and producing anew set of results (0805) is re-run. If the user selects one of thesuggested MemoryWeb tags (0806) and then selects to apply this filter(0807), the system will send this request to the User Relationship Table(0300). This portion of the Advanced Filter System is furtherillustrated in FIG. 38 .

If the Advanced Filter System is applied within the Uploads View, thesystem retrieves data for the applied filter(s) from the User'sRelationship Table and displays the relationship data (0809). An exampleof this output is later illustrated in FIG. 39 (indicator 0850).

If the Advanced Filter System is applied within the Collections View,the system retrieves data for the applied filter(s) from the User'sRelationship Table and displays the relationship data (0810). An exampleof this output is later illustrated in FIG. 39 (indicator 0852).

If the Advanced Filter System is applied within the Locations View, thesystem retrieves data for the applied filter(s) from the User'sRelationship Table and displays the relationship data (0811). An exampleof this output is later illustrated in FIG. 40 (indicator 0856).

If the Advanced Filter System is applied within the People View, thesystem retrieves data for the applied filter(s) from the User'sRelationship Table and displays the relationship data (0814). An exampleof this output is later illustrated in FIG. 39 (indicator 0854).

If the Advanced Filter System is applied within other contemplated viewswithin the Application such as Recipe, Family Trees, Timespan, etc. thesystem retrieves data for the applied filter(s) from the User'sRelationship Table and displays the relationship data (0812).

If the user decides to add an additional filter (0813), the process isrepeated when the user selects “Advanced Filter” (0801) while thepre-existing filters are still applied. An example of this process islater illustrated in FIG. 42 and FIG. 43 . If the user selects anApplication Dot-Tag, then the continuous Link of Application Dot-TagsSystem is engaged as illustrated in FIG. 30 (0700).

In FIG. 38 , the process of the Adding the First Application Dot-Tagusing the Advanced Filter is illustrated. This is a visual depiction ofthe process that was illustrated in FIG. 37 . In Stage 1 (0830), theuser selects “Apply Filters.” This takes the user to Stage 2 where theApplication generates the Apply Multiple Filters box (0831). The usercan then type in the alphanumeric text search criteria within theAdvanced Filters text box (0838). In this example, the word “Smith” wastyped within the text box. As the alphanumeric text is typed within thetext box, the application automatically generates the available filters(0836) that meet the criteria. In this example, the user selects theApplication Dot-Tag of a person named JC Smith (0832). In Stage 3,“Apply” is selected and then the application lists the ApplicationDot-Tag of a Person named JC Smith as a current active filter (0837).This filter will then be applied to each Application view that isfurther illustrated in FIGS. 39 through 41 . If the user wants to clearall the filters, they can select “clear filters” (0839).

In FIG. 39 , an illustration of the results for a Single ApplicationDot-Tag Filter for each Application view is depicted. If the AdvancedFilter is applied in the Uploads Application View (0850), the filter of“JC Smith” (0851) is illustrated and only the Digital Files that containthe person JC Smith are illustrated. If the Advanced Filter is appliedin the Collections Application View (0852), the filter of “JC Smith”(0853) is illustrated and only the Collections that contain the personJC Smith are illustrated. If the Advanced Filter is applied in thePeople Application View (0854), the filter of “JC Smith” (0855) isillustrated and only the person named JC Smith is illustrated.

In FIG. 40 , an illustration of the results for a Single ApplicationDot-Tag Filter for a date within the Uploads Application View isdepicted (0860). If the Advanced Filter is applied using a date filterwithin the Uploads Application View (0861), the filter date of “2013Jul. 4” (0876) is illustrated and only the Digital Files that containthat date are illustrated.

In FIG. 41 , an illustration of the results for a Single ApplicationDot-Tag Filter in the Location Application View is depicted (0870).Within the Location Application View the Digital Files are displayedwithin an interactive map (Google map shown as an example). The LocationView can also provide additional outputs such as a journey route thatidentifies the specific locations for an event or trip that can becustomized by users. In this view, individual or groups of Digital Filesare illustrated as photo thumbnails (see indicators 0874 and 0875)) onthe map and the user can select the thumbnail to see all the DigitalFiles with the same location (as seen FIG. 34 (indicator 1630)) or theuser can use the interactive map and narrow the map view by either usingthe zoom in/zoom out bar (0876) on the left or simply selecting the map.Note that the pinned locations include a thumbnail of the Digital File(or Collection cover) and the number of Digital Files for that location.

If the Advanced Filter is applied in the Locations Application View, thefilter of “JC Smith” (0872) is illustrated and only the Digital Filesthat contain the person JC Smith are illustrated with their geographiclocation on the map. The user can select to clear this filter (0873) orsee this Advanced Filter with the view of locations as a list (0871). InFIG. 41 , there are two illustrated on the map (0874 and 0875).

In FIG. 42 , the process of the Adding another Application Dot-Tag usingthe Advanced Filter is illustrated. Continuing on the process that wasillustrated in FIG. 38 where the first Application Dot-Tag filter of“Person: JC Smith” was applied, the ability to add a second ApplicationDot-Tag if further illustrated in FIG. 42 . As with FIG. 38 , FIG. 42 isa visual depiction of the process that was illustrated in FIG. 37 . InStage 1 (0880), the user selects “Apply Filters.” This takes the user toStage 2 where the Application generates the Apply Multiple Filters box(0881). The user can then type in the text search criteria for thesecond Advanced Filter within the Advanced Filters text box. In thisexample, the word “Abe” was typed within the text box. As thealphanumeric text is typed within the text box, the applicationautomatically generates the available filters that meet the criteria. Inthis example, the user selects the Application Dot-Tag of a locationnamed Abe Lincoln Elementary School (0882). In Stage 3 (0883), theapplication lists the Application Dot-Tags of both the Person named JCSmith (0884) as well as the location of Abe Lincoln Elementary School(0885) as part of the Current Active Filters. The user then selects“Apply” (0886) to see these filters illustrated in the ApplicationViews. This filter will then be applied to each Application view aspreviously illustrated in FIGS. 39 through 41 .

In FIG. 43 , an illustration of the results for Adding AnotherApplication Dot-Tag Filter in the Location Application View is depicted(0890). Continuing on the process that was illustrated in FIG. 42 , inFIG. 43 (0890) the Application Dot-Tag filters of “Person: JC Smith”(0891) and “Location: Abe Lincoln Elementary School” (0892) areillustrated. There is one overlapping location that contains bothfilters for a Digital File that is illustrated on the map (0893).

In FIG. 44 , the Fast Search System is illustrated (0900). Throughoutthe Application, groups or individual Digital Files can be searchedquickly using the Fast Search bar that is at the top of each ApplicationView. Once a key word or phrase is entered into this area, the user'sentire collection of Digital Tags within the Application that includesall the Digital tags are searched for potential matches. This featureallows the user to search their entire collection of MemoryWeb Tagswithin the Application and then displays the information grouped bypeople, collections, locations, documents, and recipes. The Fast SearchSystem can be searched by such items as key words (or plurality of keywords), event names, location, people, albums, star rating, file type,document type, and dates.

When a user selects the Fast Search bar from almost any Application View(0901), the user can type in alphanumeric text into the text box (0902).As the user is typing, the system sends a request (0903) to the UserRelationship Table (0300) to look up any possible MemoryWeb Tag matches.The system will then produce the request (0904) and illustrate thepotential matches by category for the user (0905). As the user types inanother letter, the process of sending a request (0903) to the UserRelationship Table (0300), producing results (0904) and producing a newset of results (0905) is re-run. If the user selects one of thesuggested MemoryWeb tags (0906), the system will send this request tothe User Relationship Table (0300). This process is further illustratedin FIG. 45 .

If the user selects a person Fast Search tag, the system retrieves datafor the person from the User's Relationship Table and displays therelationship data (0907) in the Person Profile View as illustrated inFIG. 32 (indicator 1430).

If the user selects a collection Fast Search tag, the system retrievesdata for the collection from the User's Relationship Table and displaysthe relationship data (0908) in the Collection View as illustrated inFIG. 33 (indicator (1530).

If the user selects a location Fast Search tag, the system retrievesdata for the location from the User's Relationship Table and displaysthe relationship data (0909) in the Location View as illustrated in FIG.34 (indicator 1630).

If the user selects a date Fast Search tag, the system retrieves datafor the date from the User's Relationship Table and displays therelationship data (0910) in the Uploads View as illustrated in FIG. 40(indicator 1861).

If the Fast Search System is applied within other contemplated viewswithin the Application such as Family Trees, Timespan, etc. the systemretrieves data for the search from the User's Relationship Table anddisplays the relationship data (0911). As part of the contemplatedsearch process is to also search comments related to a Digital File.

In FIG. 45 , the process of using the Keyword Fast Search isillustrated. This is a visual depiction of the process that wasillustrated in FIG. 44 . In Stage 1 (0930), the user selects the FastSearch bar at the top of one of the Application Views. This takes theuser to Stage 2 (0931) where the user can then type in the alphanumerictext search criteria within the Fast Search text box (0932). In thisexample, the word “Wrigley” was typed within the text box. As thealphanumeric text is typed within the text box, the applicationautomatically generates the available MemoryWeb Tag results (0933) thatmeet the criteria. Note how the results are organized by variousMemoryWeb Tag categories such as Person, Collection, Location, Recipe,and comments. In Stage 3 (0934), the user selects one of the results. Inthis example, the user selects the location of Wrigley Field (0935).When the user selects a specific MemoryWeb Tag, it takes them to Stage 4where the information related to that tag is displayed in thecorresponding view as discussed within FIG. 44 . For the example wherethe user selected the Location of Wrigley Field, the user was taken tothe individual locations Application View where the location of WrigleyField and the corresponding Digital Files are displayed (0936).

In FIG. 46 , the Share to Third Party Media Provider System (1000) isillustrated. This feature allows the user to share Digital Files fromMemoryWeb directly to a third party application. The process begins whenthe user selects to share a Digital File or collection of Digital Fileswithin the MemoryWeb Application (1001). Examples of where the user canselect share can be seen in FIG. 31 (indicator 0760), FIG. 33 (indicator1534), FIG. 34 (indicator 1636), and FIG. 36 (indicator 1812). Once therequest is made, the system requests the Digital File and Tag DataBlocks (1002) from the User Relationship Table (0300). The system thenretrieves the Digital File from the User Relationship Table (1003). Atthe same time, the system will also retrieve the Digital Tags from theRelationship Table (1004). The system will then inject the tags to thecorresponding EXIF Tag Data Blocks (1005). The mapping of the EXIF TagData Blocks and those of MemoryWeb Data Blocks is illustrated in FIG. 22. Note, for any tags that were modified within the MemoryWebapplication, only the new tag information will be transferred into theEXIF Tag Data Blocks. The system then combines the EXIF Tag Data Blocksand embeds them within the Original Digital File (1006). The applicationthen exports the Digital File with the new EXIF Tag Data Blocks usingthe Application Export System (1300) which then sends the Digital Fileoutside the MemoryWeb Application to the Third Party Media Provider(0501).

In FIG. 47 , the Third Party Geographical Mapping System is illustrated(1100). When Digital Files are imported into MemoryWeb, if there is anyGPS data available from the EXIF Tags (See FIG. 22 (indicators 0330,0331, 0332, and 0333)), the system will utilize this data andautomatically create a MemoryWeb location tag within the Application(See FIG. 22 (indicators 0368, 0369, 0370 and 0371)). However, if theGPS coordinates were missing from a Digital File when it was importedinto the Application (See FIG. 50 (indicators 1418 and 1419)), the usercan add the Location (which the application will automatically add theassociated GPS tags) to the Digital File using the Application DigitalTag Organization System (see FIG. 28 ). As locations are associated witha Digital File, the Application can interact with a Third PartyGeographical Mapping System to pull maps that correspond to the exactlocation of Digital Files that have a location tag (see FIG. 34(indicator 1630 and FIG. 40 , indicator 0875)). In addition, theApplication utilizes a world map view to illustrate all the locationsthat are associated to one or more Digital Files for a user within theLocation Application View (see FIG. 41 (indicator 0880)).

The Third Party Geographical Mapping System begins when a LocationApplication Dot Tag (1102) is selected (1104), the system will send arequest (1105) to the User Relationship Table (0300). Examples of whenLocation Application Dot-Tags can be selected are illustrated in FIG. 31(indicator 0768 and FIG. 35 , indicators 1723 and 1735). In FIG. 47 ifthe Locations Application View is selected (1103), the system will senda request (1105) to the User Relationship Table. The LocationApplication View can be selected from almost any Application view asillustrated in FIG. 34 (indicator 1605). When either a single locationor the world map view is selected, the system will retrieve the data(1108) from the User Relationship Table (0300) and send a request (1106)to the Third Party Geographical Mapping Provider (1101) who generatesthe map request and then sends the information back to the system forthe specific location (1107). At the same time, the Application Dot-Tagsand Digital Files associated with the location or map request areretrieved and then sent (1109) to the Locations Application view. Thesystem will combine the map information along with the ApplicationDot-Tags and Digital Files and display this information within theLocation Application View (1100). Examples of a single LocationApplication View can be seen in FIG. 34 (indicator 1630) and FIG. 40(indicator 0875), and an example of a world map view can be seen in FIG.41 (indicator 0880).

In FIG. 48 , the Share to Individual System is illustrated (1200). TheShare to an individual person or a group of people starts when a userinitiates share of a Digital File or a Collection of Digital Files(1201). Examples of where the user share functions are illustrates arein FIG. 31 (indicators 0760 and 0761), FIG. 33 (indicator 1534), FIG. 34(indicator 1636), and FIG. 36 (indicator 1812). Next, the systemrequests the Digital File and Tag Data Blocks (1202) from the UserRelationship Table (0300). They system will retrieve correspondingDigital File (or collection of Digital Files) (1203) from the UserRelationship Table.

At the same time, the system will also retrieve the Digital Tags of theDigital File from the Relationship Table (1204). The system will theninject the tags to the corresponding EXIF Tag Data Blocks (1206). Themapping of the EXIF Tag Data Blocks and those of MemoryWeb Data Blocksis illustrated in FIG. 22 . Note, for any tags that were modified withinthe MemoryWeb application, only the new tag information will betransferred into the EXIF Tag Data Blocks. The system then combines theEXIF Tag Data Blocks and embeds them within the Original Digital File(1205). The application then exports the Digital File with the new EXIFTag Data Blocks using the Application Export System (1300) which thensends the Digital File outside the MemoryWeb Application to anIndividual or Group of People (1207).

In FIG. 49 , the Application Export System is illustrated (1300). TheApplication Export System starts when a user selects the export of aDigital File within the application (1302) or has installed the MWAutomatic Uploader/Downloader Application (1308). An example of wherethe user can select the export of a Digital file within the Applicationis FIG. 31 (indicator 0751). If the user has installed the MW AutomaticUploader/Downloader Application, the export functionality of the user'sentire collection of Digital Files will be downloaded to the User'sdesired folder on their computer with the Digital Tags embedded withinthe Digital Files. If neither a user initiated download nor the MWAutomatic Uploader/Downloader Application is not used, then theApplication Export is not initiated (1309). For either a user initiateddownload or one using the MW Automatic Uploader/Downloader Application,the system requests the Digital File(s) and Tag Data Blocks (1303) fromthe User Relationship Table (0300). They system will retrievecorresponding Digital File (or collection of Digital Files) (1304) fromthe User Relationship Table. At the same time, the system will alsoretrieve the Digital Tags of the Digital File from the User RelationshipTable (1305). The system will then inject the tags to the correspondingEXIF Tag Data Blocks (1306). The mapping of the EXIF Tag Data Blocks andthose of MemoryWeb Data Blocks is illustrated in FIG. 22 . Note, for anytags that were modified within the MemoryWeb application, only the newtag information will be transferred into the EXIF Tag Data Blocks. Thesystem then combines the EXIF Tag Data Blocks and embeds them within theOriginal Digital File(s) (1307). The application then exports theDigital File(s) with the new EXIF Tag Data Blocks to the desired StorageSystem of the user (1301).

In FIG. 50 , there are three charts for the Digital File Image FileDirectory Data Blocks of JPG Photo within Microsoft Before and AfterMemoryWeb. This Figure is meant to demonstrate how the EXIF Tag DataBlocks for a Digital File (in this example a JPG file) prior to the useof MemoryWeb Application appear and then how these EXIF Tag Data Blocksare populated with Digital Tags upon export from the MemoryWebApplication.

The first chart illustrates common EXIF Tags (Data Blocks) (1401) andlists certain common the EXIfTool Family 1 Group names that aredisplayed in the file properties of a JPG file when using MicrosoftWindows (these are the same EXIF Tag Blocks that were illustrated inFIG. 22 (indicator 1320)). In the second chart (1402), the Digital Tagsassociated with the original Digital File are displayed. In the thirdchart (1403), the updated Digital Tags for the same original DigitalFile once exported from the MemoryWeb Application is displayed.

In the second chart (1402), the original Digital File prior to import tothe MemoryWeb Application did not have Digital Tags for data blocks suchas Description Rating (1416), Description Comments (1417), GPS Latitude(1418), GPS Longitude (1419). Also in the second chart the Digital Tagsfor the data blocks of File Folder Path (1420) and File Date Created(1421) are illustrated.

In the third chart (1403), the original Digital File that was exportedfrom the MemoryWeb Application now contains new or modified Digital Tagsfor certain data blocks. For example, a star rating of four out of fivestars (1410) with the new MW Modified Digital File is now associatedwith the Description Rating (1404) where it was blank (1416) with theoriginal file before using the MemoryWeb Application.

Another example is the listing of MemoryWeb Tags within the DescriptionComments data block (1411) as: CAPTION: Jackson and JC's first day atschool!, PERSON: Jackson Smith, JC Smith, LOCATION NAME: Abe LincolnElementary School, COLLECTION: First Day of School, COLLECTION: Jacksonand JC Photos 2013, DATE: Aug. 28, 2013. All of these Digital Tags arenow associated with the Description Comments (1405) where it was blank(1417) with the original file before using the MemoryWeb Application.

Also updated in the MW Modified Digital File are the GPS Latitude (1412)and GPS Longitude (1413) as Digital Tags that were assigned in theMemoryWeb Application using the location feature with the ApplicationDigital Tag Organizer System. These tags now replace the blank tags(indicators 1418 and 1419) that were in the original file before usingthe MemoryWeb Application.

A final example is how the date was modified in the MemoryWebApplication where a new date of Aug. 28, 2013 (1415) was assigned to theDigital File. This replaced the old date that was originally tagged witha date of Nov. 1, 2013 (1421). In a typical Digital File, only the dateand perhaps the GPS location if taken with certain newer photo device ispre-populated in a Digital File. For the example in FIG. 50 , theDigital File may have been created or scanned on Nov. 1, 2013, but withthe MemoryWeb Application Digital Tag Organizer System the user was ableto correctly assign the date the photo was taken and now this date isalways part of the Digital File within the MemoryWeb Application, butalso when the Digital File is exported from MemoryWeb.

A benefit of the Export System is that users can export a single DigitalFile or their entire set of Digital Files (using the MW AutomaticUploader/Downloader Application), with all the updated Digital Tags fromthe MemoryWeb Application embedded within the Digital File(s). Thisfeature is unique as it will allow the users to back up their files toanother source (e.g., external computer hard drive) or to transport itto another venue (e.g., another website that is used for viewing and/orsharing Digital Files such as a social media website) where it can beviewed with these Digital Tag attributes. This export feature canprovide users with the advantage of never losing key data that wasstored simply because the user chooses to move its Digital Files to anew digital system.

The application also contemplates the use of a Family Tree ApplicationView where the individual people that have been created within theApplication can be displayed with family relationships. This view canillustrate interactive family trees where one can see the family tree ofan individual or family. Any family relationships created in the user'spersonal profile are already pre-populated by the Application for theFamily Tree View. If a user selects on an individual within the familytree, it will take them to the people profile Application View of thatperson. Family Trees can quickly be viewed with the family treedrop-down sort feature. As with other areas within the Application, thefamily tree view can be narrowed down using an Advanced Filters System.For matching family members, the system will have drag/dropfunctionality to make new associations to a family tree. It is alsocontemplated that various family tree views could be displayed (e.g.,pedigree chart, fan chart, directs descendants chart, etc.). Inaddition, it is contemplated that family tree relationships from eitherdata files (e.g., GEDCOM files) or other sources (e.g., Family Searchdatabase) would either be imported into the user's versions of theApplication or utilize these sources in associating the family treeinformation.

Another Application View that is contemplated is Timespan or Timeline.The Timeline Application View will have an interactive timeline todisplay the dates within the Digital Files of the Application for auser. The timeline view acts as an interactive filter or funnel ofDigital Files whereas when the user starts to define the parameters ofdates towards the bottom, the information above it is filtered todisplay the major groups of Digital Files that meets the selected daterange criteria in various formats until you are able to view anindividual Digital File. This funnel approach is designed to allow theuser to appreciate the vast amount of data that can be associated with adate range, but then allow them to filter the information with theuser's desired criteria. This will be a very useful tool when users wantto see the growth and progress of an individual as well as memorialize alifetime of a friend or family member.

While the disclosure is susceptible to various modifications andalternative forms, specific exemplary embodiments thereof have beenshown by way of example in the drawings and have herein been describedin detail. It should be understood, however, that there is no intent tolimit the disclosure to the particular forms disclosed, but on thecontrary, the intention is to cover all modifications, equivalents, andalternatives falling within the spirit and scope of the disclosure asdefined by the appended claims.

1.-29. (canceled)
 30. A computer-implemented method comprising:displaying, on an interface of a client device, a year selectableelement, a month selectable element, and a day selectable element;receiving, via the interface of the client device, a first user input,the first user input being associated with one or more of the yearselectable element, the month selectable element, and the day selectableelement; responsive to the first user input, displaying, on theinterface of the client device, images associated with a first subset ofa plurality of digital files while also displaying the year selectableelement, the month selectable element, and the day selectable element,the first subset of the plurality of digital files being associated withthe first user input; subsequent to receiving the first user input,receiving, via the interface of the client device, a second user inputassociated with a first digital file in the first subset of theplurality of digital files; subsequent to receiving the second userinput, displaying, on the interface of the client device, a detail view,the detail view including (i) a first image associated with the firstdigital file in the first subset of the plurality of digital files and(ii) a location selectable element associated with a location, thelocation selectable element being overlaid on the first image; andsubsequent to receiving an input associated with the location selectableelement via the interface of the client device, displaying a locationview on the interface of the client device, the location view including(i) a name associated with the location and (ii) a second imageassociated with the location.
 31. The method of claim 30, wherein thelocation view further includes the first image.
 32. The method of claim30, wherein the second image associated with the location is associatedwith a second one of the plurality of digital files.
 33. The method ofclaim 30, wherein the name associated with the location includes (i) acommon name for the location, (ii) a street address associated with thelocation, or (iii) both (i) and (ii).
 34. The method of claim 33,further comprising, subsequent to displaying the location view,receiving, via the interface of the client device, a third user inputassociated with sharing to a third party the second image associatedwith the location.
 35. The method of claim 33, wherein the detail viewfurther includes a map image associated with the first digital file, themap image including an indication that indicates a location associatedwith the first digital file.
 36. The method of claim 30, wherein thelocation selectable element includes information associated with thelocation, and wherein the information includes the name associated withthe location.
 37. The method of claim 30, wherein the locationselectable element has a dot shape.
 38. The method of claim 30, whereinthe plurality of the digital files includes images and videos.
 39. Themethod of claim 30, wherein the detail view further includes a personselectable element associated with and identifying a person, the personselectable element being overlaid on the first image, wherein a secondsubset of the plurality of digital files is associated with the person.40. The method of claim 39, further comprising, responsive to an inputassociated with the person selectable element via the interface of theclient device, displaying a person view on the interface of the clientdevice, the person view including (i) a name associated with the personand (ii) images associated with at least a portion of the second subsetof the plurality of digital files.
 41. The method of claim 40, whereinthe person view further includes a selectable map image, and the methodfurther comprises, responsive to an input that is indicative of aselection of the selectable map image in the person view, displaying amap view on the interface of the client device, the map view including:an interactive geographic map; a first location selectable thumbnailimage positioned at a first location on the interactive geographic map;and a second location selectable thumbnail image positioned at a secondlocation on the interactive geographic map.
 42. The method of claim 41,further comprising: responsive to an input that is indicative of aselection of the first location selectable thumbnail image, displaying afirst location view on the interface of the client device, the firstlocation view including (i) a first location name associated with thefirst location on the interactive geographic map and (ii) imagesassociated with a third subset of the plurality of digital files, thethird subset of the plurality of digital files including digital filesassociated with the first location on the interactive geographic map;and responsive to an input that is indicative of a selection of thesecond location selectable thumbnail image, displaying a second locationview on the interface of the client device, the second location viewincluding (i) a second location name associated with the second locationon the interactive geographic map and (ii) images associated with afourth subset of the plurality of digital files, the fourth subset ofthe plurality of digital files including digital files associated withthe second location on the interactive geographic map.
 43. The method ofclaim 40, further comprising, responsive to an input that is indicativeof a selection of a first one of the images in the person view,displaying a slideshow on the interface of the client device, theslideshow including a plurality of images associated with the person.44. The method of claim 40, wherein the first person view furtherincludes a collection selectable element associated with the firstperson, the method further comprising, responsive to an input associatedwith the collection selectable element, displaying a collection, thecollection including images associated with the first person.
 45. Themethod of claim 30, wherein a first one of the images associated withthe first subset of the plurality of digital files is a firstrepresentative image associated with a first group of digital files anda second one of the images associated with the first subset of theplurality of digital files is a second representative image associatedwith a second group of digital files.
 46. The method of claim 45,further comprising: responsive to receiving third user input that isassociated with the first representative image, displaying, on theinterface of the client device, images associated with the first groupof digital files; and responsive to receiving fourth user input that isassociated with the second representative image, displaying, on theinterface of the client device, images associated with the second groupof digital files.
 47. The method of claim 46, wherein the first group ofdigital files is associated with a first album based on a first daterange and the second group of digital files is associated with a secondalbum based on a second date range.
 48. The method of claim 47, whereinthe displaying the images associated with the first subset of theplurality of digital files further includes displaying firstalphanumeric text associated with the first representative image anddisplaying second alphanumeric text associated with the secondrepresentative image.
 49. The method of claim 48, wherein the firstalphanumeric text associated with the first representative imageincludes a first year and the second alphanumeric text associated withthe second representative image includes a second year.
 50. The methodof claim 30, further comprising: accessing, via a network, a filerepository; and receiving, by the client device via the network from thefile repository, the second image associated with the location.
 51. Adigital file storage system comprising: one or more non-transitorycomputer-readable storage media storing a plurality of digital files andinstructions; and one or more processors, configured to execute theinstructions to: display, on an interface of a client device, a yearselectable element, a month selectable element, and a day selectableelement; receive, via the interface of the client device, a first userinput, the first user input being associated with one or more the yearselectable element, the month selectable element, and the day selectableelement; responsive to the first user input, display, on the interfaceof the client device, images associated with a first subset of theplurality of digital files while also displaying the year selectableelement, the month selectable element, and the day selectable element,the first subset of the plurality of digital files being associated withthe first user input; subsequent to receiving the first user input,receive, via the interface of the client device, a second user inputassociated with a first digital file in the first subset of theplurality of digital files; subsequent to receiving the second userinput, display, on the interface of the client device, a detail view,the detail view including (i) a first image associated with the firstdigital file in the first subset of the plurality of digital files and(ii) a location selectable element associated with a location, thelocation selectable element being overlaid on the first image; andsubsequent to receiving an input associated with the location selectableelement via the interface of the client device, display a location viewon the interface of the client device, the location view including (i) aname associated with the location and (ii) a second image associatedwith the location.